You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are interested into the same feature.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
Getting E-Mail notifications to work with a self-hosted setup is rather tedious and I do not have Telegram, however I do use Discord quite frequently. Discord allows sending messages through a webhook and lots of other platforms do too so this could also serve as workaround for other platforms until they are explicitly implemented.
Describe the solution you'd like
Allow setting up a webhook as notification channel. Required fields would be the URL, the body (which allows templating the content to allow it to be incorporated in a JSON structure for instance). Additionally it probably requires a request-method + content-type header field, shamelessly "inspired" by IFTTT's action:
Describe alternatives you've considered (optional)
I didn't come up with alternatives.
Additional context
I am willing to implement this, although I would probably need some guidance on where to start.
The text was updated successfully, but these errors were encountered:
How to use GitHub
Is your feature request related to a problem? Please describe.
Getting E-Mail notifications to work with a self-hosted setup is rather tedious and I do not have Telegram, however I do use Discord quite frequently. Discord allows sending messages through a webhook and lots of other platforms do too so this could also serve as workaround for other platforms until they are explicitly implemented.
Describe the solution you'd like
Allow setting up a webhook as notification channel. Required fields would be the URL, the body (which allows templating the content to allow it to be incorporated in a JSON structure for instance). Additionally it probably requires a request-method + content-type header field, shamelessly "inspired" by IFTTT's action:
Describe alternatives you've considered (optional)
I didn't come up with alternatives.
Additional context
I am willing to implement this, although I would probably need some guidance on where to start.
The text was updated successfully, but these errors were encountered: