Automation builder
Build each automation on a visual canvas: a webhook at the top, then filters, transformations, and destinations in the order they run. One webhook can feed as many destinations as you need, and you can follow the path without leaving the page.

Source






Benefits
Send a single incoming event to as many destinations as you need, with no extra endpoints to maintain.
Add steps on a canvas that lays itself out, instead of wiring things together in config files.
Every step from the webhook to the last destination is on one screen, so the shape of your pipeline is obvious at a glance.
Chat, databases, warehouses, observability, and more, all connected the same way.
Building an automation
An automation starts with a webhook and runs each step in order. Here is what you can put in between.
Start from the webhook that receives your events, then add the steps it should go through. Filters and transformations sit right in the chain, so you can see exactly what a destination receives and why.
Trigger
Shopify: order created
Filter
body.total ≥ 100
Transformation
transformBody(body)
Destination
Postgres: orders table
Destination
Slack: #sales
Not every event belongs in the same place. An If / Else step checks a condition and sends the event down a true path or a false path, each with its own steps.
Trigger
Zendesk: ticket created
If / Else
body.priority equals urgent
Destination
Microsoft Teams: on-call
Destination
Airtable: ticket queue
Run any step against the latest payload your webhook received before real traffic depends on it. Keep work in progress as a draft and publish when it is ready.
Using the latest payload received by this source
{ "order_id": 10482, "total": 249.00 }Step passed