Flow Cards
Complete reference of all card types available in the flow editor
Flow cards are the building blocks of your automation. Each card performs a specific action - sending a message, making a decision, calling an API, or leveraging AI.
Card Categories
The card panel in the editor organizes cards into 5 categories. Some entries are dropdowns that expand to reveal sub-cards.
Core
| Card | Description |
|---|---|
| Text | Send a text message |
| Question | Send text and wait for user's reply |
| WhatsApp ▸ | Dropdown with channel-specific cards (shown when a WA integration is connected) |
| ↳ Template | Send a pre-approved template |
| ↳ List Message | Scrollable list menu |
| ↳ Catalog | Product catalog |
| ↳ Product | Single product card |
| ↳ Products | Multiple product cards |
| Media ▸ | Dropdown for content cards |
| ↳ Media | Send image, video, or animation |
| ↳ Audio | Send audio file or voice message |
| ↳ Document | Send document or file |
| Buttons ▸ | Dropdown for button cards |
| ↳ Button | Text with inline/reply keyboard buttons |
| ↳ Media Button | Image/video with buttons |
| ↳ Audio Button | Audio with buttons |
| ↳ Document Button | Document with buttons |
| Note | Internal annotation (not sent to contact) |
AI
| Card | Description |
|---|---|
| AI Agent ▸ | Dropdown for AI cards |
| ↳ AI Text | Send prompt to AI, get text response |
| ↳ AI Classification | Classify input into categories |
| ↳ AI Text-to-Speech | Convert text to spoken audio |
| ↳ AI Agent | Multi-turn AI conversation with memory |
Tools
| Card | Description |
|---|---|
| HTTP Request | Call an external API (GET / POST) |
| Outbound Webhook Event | Emit a custom flow.* event to outbound webhook subscribers |
| Assign Operator | Assign chat to team member (auto or specific) |
| Reply to Comment | Post a public reply under a social post comment |
Reply to Comment takes a reply template and answers the comment publicly, under the post. Pair it with the Comment Received trigger to handle the questions that repeat under every post. See Posts & comments for the manual equivalent.
Logic
| Card | Description |
|---|---|
| Condition | Multi-branch routing with if/else logic |
| Sub-flow | Execute another flow as sub-flow with timeout/error handling |
| Wait | Pause the flow for 5 s - 30 min between any two cards (no input, no retries) |
| Wait Timeout | Add a reply deadline to the previous input card with optional retries and nudge |
Data
| Card | Description |
|---|---|
| Update Contact | Update contact profile fields |
| CRM ▸ | Dropdown per CRM provider (HubSpot / Salesforce / BigQuery) |
| ↳ CRM | Push contact data to a connected CRM |
Common Card Features
Every card has a settings panel (right sidebar) where you configure:
- Content - Message text, media, prompt, etc.
- Variables - Use
{{variableName}}to insert dynamic values (see Variables). - Connections - Input and output ports that define the execution path.
Operations Cost
Each card type has an operational cost when executed:
| Cost | Card Types |
|---|---|
| 0 ops | Note, Ghost, Order - nothing is sent |
| 1 op | Text, Button, Media, Audio, Document, Question, Sub Flow, Update Contact, Assign Operator, Wait, Outbound Webhook Event, Reply to Comment, and the WhatsApp cards (Template, Catalog, Product, List Message) |
| 2 ops | Media Button, Audio Button, Document Button, Condition, HTTP Request, Wait Timeout, and the AI cards (AI Text, AI Classification, AI Agent, AI Text to Speech) |
| Per field | CRM - charged by the number of fields written, not as a flat card cost |
The AI cards cost a flat 2 ops like any other advanced card, plus AI ops for the tokens they consume. The two are metered separately against separate limits - see Ops & usage.
The rule behind the table: a card that puts a message on a channel costs at least one op; a card that only does internal work costs none.