A lead waits a full day
The form arrives at night and the manager sees it in the morning. By then the person has written to two competitors, and the click you paid for is simply gone.
Workflows instead of chains of manual steps
Lay the scenario out on a canvas: what starts it, what happens next, and where the result goes — an email, an HTTP request, a Meta CAPI event, a lead record. Hit Test to run the draft and inspect every step's output before anything goes live.
Where routine eats a marketing team's week
Integrations rest on one person
A server script only one developer understands breaks the first time an API changes — and nobody can explain why the events stopped arriving.
Nobody notices what broke
The automation “seems to work” until someone happens to spot that no email has gone out for three weeks. With no run history, there is nothing to investigate.
Three steps to a workflow that actually runs
Pick the trigger
A record event (a lead or campaign created or updated, a conversion recorded), a schedule, an inbound webhook, or a manual run from the builder.
Assemble the steps
Fourteen step types: HTTP request, email, Meta CAPI event, lead record create, update, find and delete, filter, branch, loop, delay and an AI step.
Test, then activate
The Test button runs the draft and shows what each step returned. Until you press Activate, the draft never executes on live data.
What the builder gives you
A canvas instead of a spec document
The trigger and every step are visible as a connected diagram, so a marketer and a developer read the same logic without opening code.
Four ways to start a run
A data event, a schedule down to the minute, a signed inbound webhook, or a manual run — one workflow, several legitimate reasons to fire.
Logic, not a straight line
Filters, if/else branches, a loop over a list and a delay until the right moment let a workflow survive real data instead of ideal data.
Leads inside the system
Workflows create, find and update lead records with statuses from new to converted, so the first mile does not need a separate CRM.
Signed outbound webhooks
Lead, campaign and conversion events leave as signed JSON to your URL, and the delivery log shows attempts and the receiver's response.
A history of every run
Each run shows per-step status and the error code; a failing step can retry up to three times or be skipped without taking the workflow down.
In numbers
- 14
- step types available in the workflow builder
- 4
- trigger types: event, schedule, webhook, manual
- 100
- steps — the maximum size of one workflow
Questions about the workflow builder
Do I need to know how to code?
No. The trigger and the steps are dragged onto the canvas and each step is configured in a form. A JavaScript code step does exist, but it is switched on by the administrator of the installation and is not needed for ordinary workflows.
What can start a workflow?
Four trigger types: a data event (lead created or updated, campaign created or updated, conversion recorded, Meta lead synced), a schedule, an inbound webhook over GET or POST, and a manual run from the builder.
Can I test a workflow before turning it on?
Yes, that is what the Test button does: it runs the draft and the runs panel shows what each step returned. A draft is not live until you press Activate, so experiments never touch the version that is currently running.
What happens when a step fails?
It depends on how you configured that step. You can enable retries, which gives the step up to three attempts, or let the workflow continue and mark the step as failed safely. A whole run is capped at ten minutes and then stops with a timeout error.
How do I send data to an external system?
Two ways: an HTTP request step inside the workflow, or an outbound webhook that posts signed JSON to your URL on the events you choose. The signing secret is shown once, and the delivery log records status and attempt count for every call.
Build your first workflow today
A draft takes a minute, runs under the Test button, and only goes live when you decide. Until then it does not send a single email.