-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
talk:bot:install URL argument syntax and purpose unclear in documentation. #10560
Comments
Cloned the source and searched for the file that gave me that output, and it seems the only criteria it looks for is that the string starts with Edit: thinking about it more, I realized this is for outgoing messages - for the bot to receive. I still think the documentation could be worded more clearly on that (especially since it should probably be optional 🤔) but I'll close this since it seems less likely to be needed than I originally thought... |
Hi there, so the bots were designed to always be bi-directional based on "webhooks" and similar to bots in all kind of other software you would reach them by sending them messages. The
It is, the cases where the bot will run on the same server as the Nextcloud might be rather limited (mostly for home instances, but not for bigger installations). If your bot is local and doesn't need input |
Hi @nickvergessen , thanks for your response. I was able to get to this point doing essentially what you said (I had the idea to "cheat" already, and wanted to see if it would work out - seems it was the right way to go):
Admittedly this is no longer part of my "issue" with the documentation, I think this part really is just me not completely understanding, but what would be the full URL I send messages to. Let's say I have a chat located at Edit: And I just realized you made this pull request LOL - cool stuff. |
Hey, have you managed to set up the bot eventually? I'm trying to create one with the same purpose but I also don't understand what URL I need to send messages to. |
See https://nextcloud-talk.readthedocs.io/en/latest/bots/#sending-a-chat-message for documentation |
Well I've been staring at this for the past 2 hours with no success. I'm trying to configure a Webhook in GitLab that should just post the received message from GitLab in a chat.
However, after just inspecting the sent test requests.. I believe it's has something to do with the headers, because there sure is no X-Nextcloud-.. data contained and custom headers are not available. Not sure how to further approach this. |
You will need to have a script inbetween that verifies GitLab and then signs the request with your secret and sends it to the Nextcloud.
It's the "conversation token", so the part of the URL after
That is correct. See the code block inside |
I see.. so assuming I have the script, what do I do with it? It sounds like I'd need some 3rd party listening-signing-forwarding service inbetween. Is there some solution that is "usually" used for this? |
You can also have that on the same server. I will try to publish one of my bots that connects our hackerone program https://hackerone.com/nextcloud/ with a talk room later this week |
I published it at https://github.com/nextcloud/hackerone_bot |
Perfect, thank you! |
How to use GitHub
I'm trying to follow this documentation to create a webhook for sending messages only.
Here is most of the command I'm trying to run:
occ talk:bot:install --output=json --no-setup --feature=none -vvv -- "Server Alerts" "$(cat talk-pass)"
but I can't figure out the URL argument (or what it's even for).This page shows that it is a required argument - which confuses me as the first page I linked shows (as best I can tell) to send a message I will send data to
<website>/ocs/v2.php/apps/spreed/api/v1/bot/<secret_key>/message
. That is clearly a URL, and a unique one at that, so what more I would need I'm not sure. The second issue is that it doesn't elaborate on how this should look. I tried passing"alert"
and"/alert"
but both result in the same message "The provided URL is not a valid URL". The only text given on the webpage is "Webhook endpoint to post messages to (max. 4000 chars)" which tells me nothing honestly.Server configuration
Nextcloud Version: 27.1.0
The text was updated successfully, but these errors were encountered: