Automation builder

See the whole pipeline at a glance

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.

Automation builder / invoice.paid

Source

ProxyHook
Slack
Datadog
Discord
Postgres
AWS S3

Benefits

Why teams use it

One webhook, many destinations

Send a single incoming event to as many destinations as you need, with no extra endpoints to maintain.

Build visually

Add steps on a canvas that lays itself out, instead of wiring things together in config files.

Follow the path

Every step from the webhook to the last destination is on one screen, so the shape of your pipeline is obvious at a glance.

Plenty of destinations

Chat, databases, warehouses, observability, and more, all connected the same way.

Building an automation

Steps, branches, and a safe way to ship

An automation starts with a webhook and runs each step in order. Here is what you can put in between.

Chain steps after a webhook

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.

  • Filter steps that stop events which do not match
  • JavaScript transformation steps that reshape the payload
  • As many destination steps as you need
  • The canvas lays itself out as you add and remove steps
Automation / new orders

Trigger

Shopify: order created

Filter

body.total ≥ 100

Transformation

transformBody(body)

Destination

Postgres: orders table

Destination

Slack: #sales

Branch with If / Else

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.

  • Route urgent events one way and everything else another
  • Each path gets its own filters, transformations, and destinations
  • Both paths stay visible on the same canvas
Automation / support tickets

Trigger

Zendesk: ticket created

If / Else

body.priority equals urgent

True

Destination

Microsoft Teams: on-call

False

Destination

Airtable: ticket queue

Test it, then publish

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.

  • Test a step with a real payload from your webhook
  • Save as a draft and publish when it is ready to go live
  • Every step has its own configuration, test, and logs tabs
Step / Test
ConfigurationFilterTestLogs

Using the latest payload received by this source

{ "order_id": 10482, "total": 249.00 }
Step passed
Save as draftPublish

Ready to dive in?
Create your free account today.