Flows

A flow is a sequence of steps on a canvas; travellers move through it; it starts from a page, a form, a webhook, a schedule or an agent.

/flows lists your flows; open one to edit it on the canvas.

The pieces

• Flow — a named sequence with a purpose (a nurture, a checkout, a report).
• Step — one node on the canvas: a page to show, an email to send, a delay, a condition, a query, a call to an agent. Steps have inputs and outputs; you draw lines between them. See Step types.
• Traveller — one run through the flow: a visitor, a subscriber, a record. A traveller carries data (what it has collected so far) and its position. Travellers can wait — for a delay, a webhook, an agent — and resume later. See /travellers.
• Execution — the log of one run, step by step, with the data at each point. See /executions.

How a flow starts

• From a page — a URL of type Flow, or a form on a page that posts into the flow.
• From a webhook — an outside system calls your flow's webhook address. See Webhooks and credentials.
• On a schedule — a schedule-trigger step runs the flow at set times.
• From an agent or another flow — an agent's flow-trigger tool, or a step that spawns another flow.
• As a journey — the site's own registration, login, verification, onboarding or checkout runs as a flow. See Journeys.

Building a flow

Add steps from the palette, connect outputs to inputs, click a step to configure it. Every value a step needs can be typed or taken from the traveller's data with a {{path}} placeholder — {{data.email}}, {{data.order.total}}. Save, then test by running it yourself and reading the execution.

Where flows show up

The APACS section has its own view of the flows that are email sequences; the Newsletters section shows those tagged as drips. They are the same flows.