Support custom HTTP method, headers & body in webhooks

[paulo-rossy]

Hello team!

In my workflow I need to call an external service every time a ticket is created. I can achieve this with polling, but I would much rather rely on webhooks.

While digging through the codebase I saw that webhook support is already built-in, yet the current model seems inflexible: I can’t specify

• the HTTP method (e.g., POST, PUT)
• custom headers (for authentication, content type, etc.)
• or a request body template

My service authenticates via a cookie sent in the header, and right now there’s no way to set that cookie with the existing webhook implementation.

Could you clarify whether these features are currently possible?
If not, I’d be glad to open a PR that extends the webhook model to allow custom method, headers and body.

Thanks for your time!

[SavelevMatthew]

Hi, thanks for the questions.

We do have MVP webhook functionality in our platform, however most services, including ours, don't offer the level of flexibility you need.

Our webhooks allow you to specify a set of fields and filtering for models, similar to GQL queries, however it seems that we won't be able to allow any flexible body transformation logic (JSON to JSON or any other content-type) as running dynamic arbitrary code on the server is bad from a security perspective.

Regarding authorization, most systems with webhooks work as follows: the data sent is signed using an encryption key issued to the recipient, and the signature is sent in the body or in the header. The recipient, having the signature, then signs the data itself and compares the signatures, thus verifying the payload. That's the thing we've planned to implement in a future.

Ability to set an HTTP-method seems ok to me, it's also not a popular feature, but I think I saw it in few services.

A common recommended flow for working with webhooks usually involves some ETL service (e.g. n8n, zapier, flowise, windmill) that would accept the data, validate the signature / ip addresses, then transform it to the format needed by a particular hook user and send it to one or more other services