Automations
Filter, transform and forward webhooks
When a request arrives and matches your conditions, webhook.stream reshapes it and sends it on. It is the part of a workflow tool you actually needed, without the rest.
Three parts, in order
1. Filter: decide when it runs
Conditions compare a field of the request with a value. All conditions must hold. Fields can come from the JSON or form body, the headers, the query string or the request itself.
| Field | Operator | Value | Runs when |
|---|---|---|---|
body.type | equals | invoice.paid | The event is an invoice payment |
headers.x-github-event | equals | release | GitHub sent a release event |
body.data.amount | is greater than | 10000 | The amount is over 100.00 |
body.ref | ends with | /main | The push was to main |
body.customer.email | exists | The payload has a customer email |
2. Transform: build the request the destination expects
The body is a template. Double braces insert values from the incoming request, and filters after a pipe adjust them.
{
"event": "{{body.type}}",
"customer": "{{body.data.object.customer_email | lower}}",
"amount": "{{body.data.object.amount_paid}}",
"items": "{{body.data.object.lines.data}}",
"received_at": "{{request.timestamp}}",
"source_ip": "{{request.ip}}"
}Two details make this dependable:
- Types are preserved. When a value in the template is exactly one placeholder, the result keeps its type.
"{{body.data.object.amount_paid}}"becomes the number4900, and"{{body.data.object.lines.data}}"becomes the whole array. - The output is always valid JSON. Values are inserted structurally, not pasted into text, so a customer name with a quotation mark in it cannot break the payload.
The editor shows the rendered result for the request you are looking at, updating as you type.
3. Deliver: send it
Choose the method and URL, add any headers the destination needs (an Authorization header, for example), and save. You can also skip the transformation and relay the original body and headers untouched, which keeps the sender's signature verifiable at the destination.
Presets
Forward to my API
Relay each request unchanged to a staging server or a second environment.
Notify Slack
Post a formatted message through a Slack incoming webhook.
Notify Discord
Post to a channel through a Discord webhook.
Notify Telegram
Send a message with your bot's sendMessage method.
Push with ntfy
Send a push notification to your phone through an ntfy topic.
Custom request
Any method, any HTTPS URL, any body.
Things people build with it
- A payments channel. Stripe events filtered to failures and large payments, posted to Slack in plain language.
- A fan-out. One provider webhook relayed to staging and to a colleague's environment at the same time.
- A format adapter. A service that only sends its own JSON shape, reshaped into the payload another API accepts.
- A phone alert. A push notification through ntfy when a long-running job calls back.
- A recorder. Every delivery kept in the inspector with its outcome, so you can see what was sent and what came back.
Limits and safeguards
| Free | Pro pass | |
|---|---|---|
| Automations per URL | 3 | 10 |
| Deliveries per day | 1,000 | 10,000 |
| Deliveries per minute | 30 | 120 |
| Timeout per delivery | 8 seconds | |
A relay that anyone can configure is an obvious target for misuse, so automations are fenced in: HTTPS destinations only, no private networks, no redirects, hard budgets per URL, and identifying headers on every request. The security overview has the details.
Frequently asked questions
Is this a replacement for Zapier or Make?
For one job, yes: reacting to an incoming webhook by sending an HTTP request somewhere else. It has no app directory, schedules or multi-step workflows. If all you need is to filter, reshape and forward a webhook, it is quicker to set up and easier to reason about.
Can I run my own code in a transformation?
No, and that is deliberate. Transformations are templates with a fixed set of filters. They cannot loop or run arbitrary code, which keeps them predictable and safe to run on shared infrastructure.
What happens when a delivery fails?
The attempt is recorded with its status code, timing and the start of the response, and shown on the request's Deliveries tab. Deliveries are not retried automatically. After 15 failures in a row an automation pauses itself and tells you why.
Which destinations are allowed?
Any public HTTPS URL on the standard port. Private and local addresses, IP literals, embedded credentials and webhook.stream itself are refused. Redirects are not followed.
How do recipients know where a request came from?
Every delivery carries a webhook.stream User-Agent and X-Webhook-Stream-Endpoint and X-Webhook-Stream-Request headers. If you receive unwanted requests, send those headers to abuse@webhook.stream and the endpoint will be disabled.