Skip to content
Book a demo Start building

Build automations without writing code.

Pick a trigger, add the apps and steps you need, and publish. Runs are saved as they go, so a crash or a deploy doesn't lose work. Every run is kept for 30 days so you can check it and retry.

Start buildingBook a demo
Live Test
WebhookNew submissionTrigger
Hot lead
SlackNotify sales
Just browsing
HubSpotAdd to nurture

Use the apps you already have

Build from 760+ integrations, and use a code or HTTP step for anything they don’t cover.

Branch and repeat

Send the run down different paths, and repeat a set of steps over every item in a list.

See what every run did

Each run keeps its inputs and outputs for 30 days, so you can retry the step that failed.

What else the builder does.

Any Trigger

A webhook, a schedule, an event in one of your apps, or a manual run.

Test Every Step

Run a single step on real data and read its output before you publish.

Code Steps

Write TypeScript in any step you need it.

Routers and Loops

Branch on a condition, catch everything else, and repeat steps over a list.

Runs That Resume

A crash or a deploy picks the run up from the last finished step.

Build by Asking

Describe what you want, and it gets built.

Draft and Publish

Publishing locks that version. Editing a live automation opens a new draft.

Open Source

Run the MIT-licensed core yourself with Docker, Compose or the Helm chart.

Common questions.

There is no cap per organization on our cloud, and no limit in the license when you self-host. Each worker handles 5 jobs at a time, and jobs queue instead of being dropped when you go over. A single run is capped at 10 minutes by default, which you can raise when self-hosting.

Every run appears on the Runs page with its status, the step it failed on, the error it returned, and the input and output of each step. Everyone in the project gets an email on failure, and a one-step automation can forward that to Slack, Teams or PagerDuty.

Both. Every webhook-triggered automation gets its own URL, and with a response step it answers right away, so you can publish one as an HTTP API without code. Separately, each automation is plain JSON you can export and re-import over the REST API, which is on paid plans.

A stateless app, one or more stateless workers, PostgreSQL, Redis, and optionally S3-compatible storage for run logs. Docker, Docker Compose and our Helm chart all work. PostgreSQL is required, and we support containerized deployments only.

One credit for the whole run, however many steps it has. Branching, loops and code do not change it. A polling trigger that finds nothing is free, and so are test runs from the builder.