AI Collector
The AI Collector is a multi-turn agent that gathers a set of data points — called slots — through one natural conversation. Instead of chaining many question nodes, you describe who the agent is, what it must accomplish and which fields it needs; the AI asks, re-steers off-topic answers and keeps going until every required slot is filled. On WhatsApp, voice notes are transcribed, images and documents are ingested, and shared locations are enriched automatically before each turn.
Everything collected is stored in a single object variable, so downstream nodes can read each field with {{variable.field_name}}.
Configuration
| Option | Description |
|---|---|
| Identity | The agent's persona and tone. Supports {{variables}} |
| Rules | Constraints and policies the agent must respect. Supports {{variables}} |
| Goal | The internal objective the agent pursues. Supports {{variables}} |
| Preferred Flow | Guides the order and approach, for example "ask one field at a time". Supports {{variables}} |
| Slots | The fields to collect. Each slot has a field name, a type (String, Number, Date, Boolean, Object, Array or Attachment), a description and a Required flag |
| Only if... | Per-slot condition: the slot only activates when another slot holds the expected value |
| Max turns | Anti-loop limit before giving up (default 6) |
| Include previous context | Shares the initial template, if any, and the recent messages with the agent so it does not re-ask what was already answered. On by default |
| Max previous messages | How many recent messages to include when previous context is on (default 10, between 1 and 30) |
| Give-up message | Optional message sent to the customer when turns run out |
| Re-confirm or edit on re-entry | If the customer writes again after everything was collected, the agent resumes in context — re-confirms or fills what was missing — instead of skipping the node |
| Response Variable | Object variable where all collected slots are stored. It is created automatically |
Output Handles
| Handle | When |
|---|---|
| Success | Every required slot (including slots activated by Only if...) has been collected |
| Give up | Max turns was reached without completing the required slots. The Give-up message, if any, is sent first |
Things to Know
The engine decides when the node is done. Even if the AI believes it finished, the node stays open while required slots are pending — including slots that an Only if... condition just activated mid-turn.
An empty answer is not an answer. A slot whose value is an empty text does not count as collected, so the agent asks for it again. 0 and false are legitimate answers and do count.
Only if... is typed by the field it references. The text true matches a Boolean slot holding true, and 30 matches a Number slot holding 30, so conditional slots work regardless of how the value was captured.
Multimodal input is handled before the AI runs. On WhatsApp, audio is transcribed, an image or document fills the first pending Attachment slot with a reference to the file the customer sent (or is read for data when no Attachment slot is pending), and shared locations are geocoded deterministically — the model only reasons over the result. On the web channel the agent works over text.
Turns are counted per entry. When Max turns is exhausted the node gives up, sends the Give-up message if you wrote one, and leaves through Give up.
Without a Response Variable the data is not lost. The node falls back to a name of its own per node, so an already published flow keeps collecting; name the variable anyway so downstream nodes can read it.
Re-entering the node. If every slot is already collected, the node is skipped and the flow advances, unless Re-confirm or edit on re-entry is on: then the agent resumes in context over all slots.
No opening question. The opening line comes from the agent, in context, never from a canned greeting. If the agent produces nothing to say on entry, nothing is sent, the node stays waiting for a reply the customer has no reason to write, and a warning notice is left on the conversation: "The agent produced no opening question... Review the node's goal and slots." That is where to look when a flow seems stuck on this node.
On the web channel the typing bar stays open while the collector is waiting, so the customer can keep answering in free text.
Connect both outputs. The publish gate blocks the flow if either Success or Give up is left unconnected. Use the Give up branch to hand off to a human or a simpler question path: it is what the customer experiences when turns run out. The flow check run by the flow assistant also reports an AI Collector with no slots configured.
Channels
Available on WhatsApp and web. Not available on email: the editor does not offer it in email flows, and if an email conversation still reaches one, the engine leaves the warning notice "Unsupported node type for email" and continues through the error edge.