-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
Multiple webhooks #804
Comments
For your use case, you can definitely currently send to both (use gotify and ntfy). Setup gotify notifications in settings > notifications > gotify and select notification type, And in settings > notifications > webhook setup ntfy with "Request Processing Failed" and "Issue Reported". |
Okay, taking gotify and ntfy was a bad example. What if I want to use ntfy but with two different topics? |
Then yes that's a legit use case. So I recommend editing the feature request so it's clear 😉 |
I'm adding support for jellyseerr in subgen to transcribe(create a subtitle with whisper) when reporting an issue with the subtitle. I'm using the webhooks for that. Also overr-syncerr also uses the webhooks for that (where i got my inspiration from :)) So that also adds conflicts (for me) because only one uri can be set |
Description
I would like to specify multiple webhooks to push different events to multiple channels. Right now it is only possible to define one webhook. Even when using something like webhook, if different events should be sent to different channels, one would have to parse the payload before forwarding it to the right channel.
So technically it is possible to push different events to multiple channels, but right now it is a big hassle combined with setting up another service. Supporting multiple webhooks would make this process a lot easier.
Desired Behavior
An example of what I want to achieve:
Right now, I can only choose one of the two. I would like to be able to specify multiple webhooks with different notification types and webhook URLs.
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: