Webhook JSON templating - Feature Request

[mr_kam 0]

Hi,

Request: Make the JSON payload of the webhook customizable.

- Ability to customize the JSON payload sent via the webhook
- Ability to use template variables such as “{{item_name}}” or “{{media_poster}}”.
- Better documentation on what is sent. In fact, you have to do a lot of testing to get the complete JSON payload. What's going on here? The documentation only says, “You can use Webhook with IFTTH.” -> Honestly, how does that help us?

For the past two days, I've been trying to use Webhook to send notifications to my Ntfy instance. It works, but not as I want it to, even with Ntfy Templating and other settings.
The current Webhook is too obscure and not very easy to use.

I don't understand why Emby Webhook is so limited. You can literally do EVERYTHING with Webhook, it's universal. No need for notification plugins or other tricks that need to be updated with the main application. Webhook is the ultimate tool for all communication (if there are no “click-click” plugins).

Remove all notifications plugings but add a REAL Webhook builder.

Now I'm using Jellyseerr webhook builder for my Ntfy instance, but it's limited to the Jellyseerr usage himself. If I manually add media in Emby, no one got the notification with poster and some comments.

[Luke 42077]

Quote

I don't understand why Emby Webhook is so limited.

Hi, its not limited, it's just in a specific json format, right?

[mr_kam 0]

1 hour ago, Luke said:

Hi, its not limited, it's just in a specific json format, right?

Nah, to facilitate exchange with other tools I think it can be interesting to add those possibilities:

- Add authentication header
- Add custom header (for exemple Ntfy can be configured also by adding customs header like X-Template)
- Choose what is send or how, like a custom json yes
 

For example, if you want use Ntfy with JSON payload, you can provide many interesting thing like attachment with URL, but in the current JSON send by Emby you can't parse it into an URL even if you have everything to do it (media id, media primary tag id). It can't be passed in the URL too because it doesn't support templating for 'attach' var, it can only do in the payload OR in the URL if it's already concatenated.

I really want to use Webhook directly from Emby, because what can be better than the final tool to notify us for some news ?

In this purpose I'll try with a private n8n instance to modify the received JSON payload, I'll probably be able to archived what I want, but it's probably overkill just for that.

Don't misunderstood my words, in every world I'll grab Emby $$ even without this feature

[Luke 42077]

I think it's an ambitious but great idea. Then perhaps many of the other notification plugins could be built on top of that.