How it works
Something happens. Something else happens because of it.
01 · Trigger
Anything in the platform can start a workflow
A form submitted, a purchase completed, a course module finished, an appointment booked or missed, a tag added, a link clicked, a page visited, a message received, a subscription cancelled. Every one of these is a trigger, because every one of them happens inside the same system.
- Form, survey and quiz submissions
- Purchases, refunds and failed payments
- Course enrolment and module completion
- Appointments booked, rescheduled or missed
- Tags added or removed, links clicked, pages visited
- Inbound messages on any channel
02 · Branch
Conditions, branches and waits on a visual canvas
Drag the logic out on a canvas rather than describing it in a form. If they bought, do this; if they didn't, wait three days and do that. Split by any field, any tag, any behaviour. Wait for a fixed period, until a specific time of day, or until a condition becomes true.
- Visual drag-and-drop workflow canvas
- If/else branching on any field or behaviour
- Wait steps — fixed delay, specific time, or until a condition
- Goals that pull contacts out when they convert
- Split-test different automation paths
- Unlimited workflows and unlimited steps
03 · Act
Then do the thing — anywhere in the platform
Send the email, add the tag, update the field, grant or revoke course access, move the deal down the pipeline, create the invoice, assign the task, notify your team, or fire a webhook to something outside. Actions reach into every module because there is only one system to reach into.
- Send emails and internal notifications
- Add or remove tags and update custom fields
- Grant, revoke or extend course and community access
- Move opportunities through a pipeline
- Create invoices, contracts and tasks
- Webhooks and API calls out to other tools
