Automated flows
Respond to customer behavior with timed, connected actions.
View as Markdown ↗How flows work
A flow starts with a trigger and moves each enrolled contact through connected actions. Contacts can wait, receive email, branch based on data, or call an external webhook.
Triggers
Start flows from customer events, list membership, or manual enrollment. Event triggers can use properties such as plan, product, value, or currency to narrow who enters.
Actions
Activate a flow
Save and review the full graph before activation. Active flows accept new enrollments; pausing stops new work while preserving the flow and its reporting.
Use a test contact and a short delay to confirm content, conditions, and external webhook responses before activating a production flow.
Everything on this page is available from code too — triggers, waits, and branches as a list of steps. See the Flows API.