A flow is a graph with a trigger followed by conditions and actions. Connect nodes in execution order and enable only after testing. A flow graph is capped at 40 steps per run — a safety limit against runaway loops.
Triggers
DM/keyword, post or Reel comment, Story reply, Story mention, new lead, lead qualified, and meeting booked.
Keyword table mode (multi-row keywords) is available on comment triggers: instead of one keyword condition per node, load a table of rows (each with its own media, keyword, match type, and reply/DM). Rows are checked in order and the first match wins — put your more specific rows above your catch-alls. This mode is currently only wired for comment triggers, not Story replies, which still take a single keyword condition.
Keyword matching has three modes: contains (default — matches on word boundaries, so "info" won't fire inside "información"), exact, and starts with. Multiple keywords in one field are separated by commas, semicolons or line breaks and matched as OR (any one of them fires it) — there's no regex mode. Leaving keywords empty matches anything.
Comment and Story triggers can be restricted to one specific post/Reel or active Story via a media picker; leaving it empty fires on any of them.
Conditions
The condition types that actually work today: keyword match, lead already qualified, lead has a specific tag, lead score above a threshold, lead sitting in a specific stage, and "this is the lead's first message."
Actions
Send a message or media, reply to or like a comment, add/remove a tag, change pipeline stage, reassign the saved brain preset, adjust lead score, turn AI on/off for the conversation, assign to a teammate, create a task, delay, or call a webhook (8-second timeout, must return success or the run fails).
An AI reply / custom instructions action is different from the rest — it's not one-shot. It hands the conversation a standing mission that keeps steering the AI's replies across future turns until that mission's steps are complete, not just for the one message that triggered it.
Delays and scheduling
A short delay (under ~15 seconds) just makes the current request wait before continuing. Anything longer is handed off to a background job that resumes the flow later — it does not hold a connection open or block anything in the meantime.
How flows interact with the normal AI agent
One-shot triggers (comment, Story reply/mention, new lead, lead qualified, meeting booked) fire once per event; after a Story-reply/mention opener, later DMs in the same thread are treated as regular messages, so the opener won't refire and the normal agent conversation picks back up automatically — unless the flow explicitly turned AI off. If several flows match the same DM/keyword event, only the first one to actually send an AI reply wins; the rest don't also reply. Several one-shot flows CAN all fire off the same single event (e.g. one flow tags the lead while another sends a DM).
There's no hard cap on the number of flows or keyword rows in the current code.