-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Webhook payload querystring for Synology Chat Integration #2813
Comments
I have created a docker container to take care of this integration. |
We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue was closed because it has been stalled for 2 days with no activity. |
This comment was marked as resolved.
This comment was marked as resolved.
My UptimeKuma says:
|
What did you put into the |
|
That is supposed to go into the |
🛡️ Security Policy
📝 Describe your problem
I am trying to post an automated notification to Synology Chat using the Webhook notification type. Synology chat expects a payload querystring parameter formatted like this:
?payload= {"text": "Uptime Kuma alert: {{check.name}} is {{check.status}}"}
I got that format from asking ChatGPT. Not sure where it got the "{{check.name}}" format because it doesn't work. What gets posted to the chat channel on Synology Chat is:
So the integration is working but the variable names don't get translated by Uptime Kuma. Again, I don't know where ChatGPT got the syntax, since I can't find an example that uses that syntax.
So my question is, is there a correct syntax that can be put in the querystring that will translate those variables into the actual values or do I need to put in an enhancement request to either allow that functionality or to add a new Notification Type for Synology Chat?
Thanks in advance for your help!
🐻 Uptime-Kuma Version
1.20.1
💻 Operating System and Arch
Ubuntu 20.04
🌐 Browser
Firefox 110.0
🐋 Docker Version
No response
🟩 NodeJS Version
No response
The text was updated successfully, but these errors were encountered: