Automations: a visual canvas that runs your funnel
Mass automations are built on one visual, node-based canvas and run on one engine — what you build on the canvas is what executes. You drag triggers, actions, conditions, and delays onto a flow, connect them, and the engine runs that flow when a real event fires. Start from the template library or a blank canvas, let AI write your email and SMS copy, and every node in the palette runs end to end. This guide explains the editor, the triggers and nodes, templates and AI, and how a run executes.
18 min read · The complete automations guide
The full-page editor & canvas
Every automation opens in its own full-page editor, built around one canvas.
Each automation opens in its own full-page editor. On the canvas, each step is a node, and edges connect them top to bottom. Every workflow starts with a trigger node and flows into actions, conditions, and delays. A Runs panel in the editor shows the automation's run history, so you can see what happened each time it fired. The old Workflows pages now lead to Automations, so there is one place to build and manage every flow.
The canvas comes with the usual flow affordances — a minimap, pan and zoom controls, and a background grid — and a Node Library palette grouped by what each node does. The Node Library shows whether each node runs, how it works, and its inputs and outputs, and node settings offer your real tags, lists, forms, funnels, and products to pick from instead of typed IDs.
- Full-page editor — every automation opens in its own editor; the old Workflows pages now lead to Automations.
- Runs panel — the editor shows the automation's run history alongside the canvas.
- Node Library — a wider palette that shows whether each node runs, how it works, and its inputs and outputs.
- Real options in settings — node settings list your actual tags, lists, forms, funnels, and products.
Three automation types
The same canvas powers event automations, build workflows, and admin sequences.
Workflows declare an automation type that frames what they're for. Funnel automations are event-driven — they fire on user actions like a form submit, a page visit, a purchase, or a quiz completion. Workflows are build-agent flows that generate funnels, copy, and content (for example: onboarding data → wireframe → copy prompts → AI copy). Admin automations are backend flows like nurture campaigns and internal notifications.
The type informs which nodes make sense and how the flow runs, but they share one canvas and one execution model, so you learn the builder once and apply it across event marketing, content generation, and backend operations.
- funnel_automation — event-driven flows triggered by user actions (form submit, page visit, purchase, quiz complete).
- workflow — build-agent flows that generate funnels, copy, and content from inputs.
- admin — backend flows — nurture sequences, internal notifications, and operations.
- One builder — all three share the canvas and execution engine, so the skill transfers.
Triggers: what starts a flow
One catalog of live triggers, grouped by source and wired to real events.
Every flow begins with a trigger, chosen from one catalog of live triggers grouped by source. Form submissions, completed orders (Stripe, PayPal, Square, and Authorize.net), page visits, and exit intent now start matching automations. CRM triggers fire on contact created, deal stage changed, and lifecycle changed, and pixel triggers let automations react to the platform's own first-party tracking.
Hub triggers fire on course enrolled, lesson completed, course completed, and offer purchased, and quiz result triggers react to how someone finishes a quiz. Messaging channels can start flows too: SMS received, Facebook lead form, and a Stripe Payment trigger are all available. Because these triggers are wired to the real events, an automation fires when the event happens — no middleman integration required.
- Forms, orders & visits — form submissions, completed orders (Stripe, PayPal, Square, Authorize.net), page visits, and exit intent.
- CRM triggers — contact created, deal stage changed, and lifecycle changed react to pipeline movement.
- Hub & quiz triggers — course enrolled, lesson completed, course completed, offer purchased, and quiz results.
- Pixel & channel triggers — pixel triggers, SMS received, Facebook lead forms, and Stripe Payment.
Actions, logic, data & AI nodes
Dozens of nodes that used to be placeholders now work end to end.
Downstream of the trigger, nodes do the work — and the palette only offers nodes that run. Communication nodes send email, SMS, WhatsApp, Slack, Discord, Messenger, and Instagram DM messages, plus push notifications to workspace members. Logic nodes shape the path with Yes/No and A/B split branching and delays, and utility steps — Filter, Router, Iterator, Aggregator, and Merger — reshape data as it moves through the flow.
Internal CRM steps create and update contacts and tags, create and update deals, and log activities. Integration steps for Stripe (payments, checkout, customers, and subscriptions), Google Sheets, Airtable, Calendly, Zoom meetings, and MCP servers now run. AI steps use OpenAI, Claude, and OpenRouter for text; fal and Replicate generate images and video with current models; and Doc from Template and Custom Document steps create documents — all on your credits. Pixel lead-score actions and Voice Call steps run too.
- Communication — email, SMS, WhatsApp, Slack, Discord, Messenger, Instagram DM, and push notifications to workspace members.
- Logic & utilities — Yes/No and A/B split branching, delays, and Filter, Router, Iterator, Aggregator, and Merger steps.
- CRM — create and update contacts and tags, create and update deals, and log activities.
- AI & media — OpenAI, Claude, and OpenRouter text; fal and Replicate images and video; Doc from Template and Custom Document — on your credits.
- Integrations — Stripe, Google Sheets, Airtable, Calendly, Zoom, MCP servers, pixel lead-score actions, and Voice Call.
Templates & Write with AI
Go from a blank canvas to a running automation in minutes.
The New button opens a searchable gallery of automation templates for funnels, forms, communities, hubs, and visitor activity. Each template shows a preview of its steps, and you can optionally have AI write the copy when you create it. The result is a ready-to-edit automation you can adjust on the canvas and switch on. Creating an automation from a template also works on older accounts, and shows the reason if something fails.
Inside email and SMS step settings, Write with AI drafts or rewrites your copy using your brand, audience, and offer context, so you don't have to write every message from scratch.
- Template library — a searchable gallery for funnels, forms, communities, hubs, and visitor activity, with step previews.
- Optional AI copy — templates can be created with AI-written copy, ready to edit.
- Write with AI — email and SMS steps draft or rewrite copy from your brand, audience, and offer context.
The AI co-builder
Describe the automation; AI lays out the nodes and edges.
You don't have to place every node by hand. An AI co-builder turns a plain-English description into a complete workflow — it picks the automation type, emits valid nodes with the right per-type config, wires the edges (including the true/false branches off condition nodes), and lays the graph out top-to-bottom with sensible spacing. A separate modify path lets AI edit an existing workflow rather than only generating from scratch.
The generator is constrained to the real node vocabulary — the same trigger, communication, logic, data, and AI node types the canvas supports — so what it produces is immediately runnable and editable. You can also start from the template library and refine the result by hand or with the AI.
- Description → workflow — AI chooses the type, emits valid nodes and config, wires edges, and lays out the graph.
- Generate or modify — one path builds from scratch; another edits an existing workflow in place.
- Constrained to real nodes — output uses the canvas's actual node vocabulary, so it's runnable immediately.
- Templates — the template library seeds a flow you can refine.
How a run executes
One engine runs what you build on the canvas, node by node.
Automations built on the canvas run on the same engine as Test/Run, so what you test is what executes when a real event fires. The engine walks the graph node by node from the trigger, follows Yes/No and A/B split branches, and delays resume on schedule. Each run appears in the editor's Runs panel.
Contact fields, contact custom fields, and custom values fill in when each run happens, so messages are personalized for the contact who triggered the run. Pick them from the new Contact group in the variable picker. Plan limits govern how many automations an account can run, consistent with the rest of the platform's tiered limits.
- One engine — canvas automations run on the same engine as Test/Run.
- Branching & delays — Yes/No and A/B split branching, with delays that resume on schedule.
- Run-time personalization — contact fields, custom fields, and custom values fill in at run time, from the Contact group in the variable picker.
- Plan-governed — the number of automations an account can run follows the platform's tiered limits.
Events fan out to enrolled automations
A pixel hit or CRM change dispatches to every automation listening for it.
Automations are wired into the platform's event stream. When the tracking pixel ingests an event — for example a content view — a dispatcher fans it out to any tenant automations registered for that trigger and starts their runs. The dispatch is fire-and-forget: a crash in an executor never breaks the pixel write that already succeeded, and missing automation tables on legacy installs soft-fail to a no-op so the public pixel route can't error.
The same pattern connects CRM movement to automations. This is the closed loop that ties the suite together: the pixel and CRM produce events, automations consume them, and actions like emails and field updates produce new events in turn — all on the same first-party data graph.
- Pixel → automations — ingested pixel events are matched and dispatched to automations registered for that trigger.
- Fire-and-forget — an executor crash never tanks the pixel write; dispatch failures are isolated.
- Soft-fail safe — legacy installs without the automations table degrade to a no-op instead of 500-ing.
- Closed loop — events drive automations, whose actions create new events — one continuous graph.