Sheet 01 · Visual workflow automation

Connect your tools.
See every step run.

Build a workflow on a canvas, test each step with real data as you go, and run it on a webhook or a schedule. When something needs a person, the run waits.

Start automating free Browse templates Free plan · no card · a working example already in your account

Your first workflow active

webhook · 5 steps · last run 14:02:11

webhook set vars condition set vars ×2

Step	In	Out	Took
New order	{ "customer": "ada lovelace", "amount": 249.99 }	same	3 ms
Tidy up the values	customer, amount, sku	{ "customer": "Ada lovelace", "reference": "WIDGET-1" }	1 ms
Is it a large order?	249.99 > 100	true → Flag for review	0 ms
Flag for review	outcome, message	Ada lovelace placed a large order (249.99).	1 ms

Fig. 1 — the example every new account starts with. Press Test on any step and this is what you see.

123 apps with ready-made operations, and any other API through its OpenAPI spec.

Browse integrations →

Sheet 02 · Watch every step run

Test one step with real data while you build.

Send a sample or the last real payload through a single step and see exactly what went in and what came out. Then open any run and read the same trace, step by step.

How testing works →

Tidy up the values set vars

Test this step Use last real payload

{
"customer": "ada lovelace",
"amount": 249.99,
"sku": "WIDGET-1"
}

Out · ok in 1 ms

{
"customer": "Ada lovelace",
"amount": 249.99,
"reference": "WIDGET-1",
"received_on": "Sep 04, 2026"
}

from: YakPipes approvals14:02

Refund of $512.50 for ana@acme.io needs your approval

Workflow “Refund requests” has paused at step 3 and will continue down the branch you pick. It waits up to 3 days.

Approve Reject

Waiting since 14:02 · survives restarts · reminder in 24 h

Sheet 03 · Wait for a person

Pause a run until someone says yes.

Add an approval step and the approver gets an email with approve and reject links. The run holds its place for days if it has to, then continues down whichever branch they choose.

See the approval template →

Sheet 04 · Any API, not just the popular ones

Paste an OpenAPI spec. Get typed steps.

Every operation in the spec becomes a step with typed fields. We keep a snapshot of the spec and warn you before an upstream change breaks a workflow.

Import a connector →

procore.yaml v2 · 148 operations

GET /rest/v1.0/projects list projects
POST /rest/v1.0/rfis create RFI
PATCH /rest/v1.0/daily_logs field renamed

Spec changed on 2 Sep: “Send daily log” uses a renamed field. Review before the next run.

Also on every plan

Formatting is included

Trim, round, reformat dates, join lists — inline, on any field. Zapier charges a task for that; here it is part of the step.

It doesn’t lose work

Waits and approvals survive restarts, retries back off and honour Retry-After, and a failed run can resume from the step that broke.

Built for AI agents too

An MCP endpoint turns your workflows into tools an assistant can call, under your quotas, with approvals gating anything risky.

Start from one of these

Templates that already run.

See all templates →

webhook set vars condition set vars ×2
Your first workflow

A working example you can run right now: it takes an incoming order, tidies up the values, and routes big orders differently from small ones.

no setup Use this
webhook approval email ×2
Ask a person before it happens

Pause the workflow and email someone an approve/reject link — the run waits for their decision, then takes a different path depending on the answer.

no setup Use this
schedule digest condition email
Send the daily digest

Once a day, empty everything collected by “Collect events for a daily digest” and send it as one email — and stay quiet on days when nothing happened.

no setup Use this

Try it with something real.

Signing up drops you into a working workflow. Press Test on a step and watch the data move. About five minutes to your first run.

Start automating free Read the quickstart

Connect your tools. See every step run.