Webhook Relay provides public endpoints which can accept webhooks and then, based on user defined rules, forward them to either public or internal destinations.
Our service has a concept of bucket which is basically a grouping mechanism that enables you to accept webhooks on multiple endpoints and forward them to one or more destinations. A newly created bucket will have a default input and will request you to create an output destination:
If it’s a public destination, add the name, HTTP URL and click ‘create output’. All received webhooks will be forwarded to that destination.
If it’s an internal destination, check ‘internal network’ and start a
Currently Webhook Relay forwards:
- Body (up to 3MB)
- URL query, for example
https://my.webhookrelay.com/v1/webhooks/2e50b993-ac45-48f7-b840-eb054b19e630?foo=bar, will be forwarded to
- Extra path that’s after your public input endpoints:
https://my.webhookrelay.com/v1/webhooks/2e50b993-ac45-48f7-b840-eb054b19e630/directory/foowill be forwarded to
Sometimes applications that send webhooks accept certain headers, status code or body. To configure these settings, go to your bucket details and click on a settings icon near the input URL that you want to configure:
Configuration looks like:
If you need more specific or dynamic configuration, consider using bidirectional tunnels with your own server on the backend.
Output configuration allows overriding request headers so users can add any headers on top:
You can also update output destination and headers through CLI: