Flows: the visual automation builder

Flows are visual automations: a trigger (what starts it) followed by steps (what happens). Build them on a drag-free vertical canvas at Automations → Flows.

The core design principle: the AI stays the closer. Flows handle the structured opening moves — deliver the link, tag the lead, notify your team — and then hand the conversation to the AI, which takes over completely.

01Triggers (what starts a flow)

• Someone comments a keyword on your post or reel (optionally a specific post).
• Someone DMs a keyword.
• Someone replies to your story.
• A lead goes quiet — no reply for a window you choose (with built-in anti-spam fences: it only fires when you spoke last, only for reasonably fresh conversations, and only once per lead per flow).
• Another tool sends a lead here — a private webhook URL unique to the flow; your CRM or any external tool POSTs a lead in and the flow starts. See Integrations.

One flow runs per conversation at a time — a lead can't be in two flows at once.

02Steps you can use

• Send a DM — your exact message.
• Reply to their comment — a public comment reply, either exact text or AI-written in your persona's voice (kept short, no links or prices on the public surface).
• Hand to AI — the AI takes over the conversation completely. This ends the flow: from here the conversation is the AI's.
• Wait — until they reply, or for a set time.
• Split — branch on replied / didn't reply, or on a tag.
• Add / remove tag, Move pipeline stage — organize leads as they move.
• Notify the team — bell notification, plus Slack/Discord ping if connected.
• Hand to human — flags the conversation for a person and pauses automation.
• Call a webhook — send the lead's info to an external URL mid-flow.
• Go to — jump a lead to any other step in the same flow, drawn as a curved connector back to the target. Use it to loop (e.g. "not sure" → wait → back to the split to re-ask) or to funnel several branches into one shared path without rebuilding it. Loops are safe: the engine caps how many times a single lead can jump, so a flow can never run forever.

03Draft → Live

Every flow starts as a Draft and sends nothing. Publishing runs a validation pass (empty messages, unreachable steps, misplaced splits are caught). Flip to Live when ready; flip back to Draft any time to pause new entries.

Each flow in the list shows when it was created, and the ⋮ menu on the right lets you edit, duplicate, or delete it. Duplicates are born as Drafts with their own webhook token, so copying a Live flow never fires anything by surprise. Deleting a flow exits any leads currently walking it cleanly.

04Test before you trust

Test it simulates a lead walking through your flow — including which branch they'd take — without sending anything real. The simulator is explicit about what it can't fake (waits are skipped; live AI classification happens only in production).

05See what actually happened

Each flow has a per-lead execution log — What happened — showing every step taken for every lead who entered, including anything that was blocked and why. The Stats toggle overlays per-step counts on the canvas so you can see where leads drop off.

06Classic rules

Simple keyword→DM rules from before the flow builder live under the Classic rules tab and keep working. New automation should be built as flows — they're strictly more capable.