Visual automation that connects
messages, logic, and action
Flow Builder is the control center for automated journeys in ChatbotX. Teams can manage flows at scale, design omnichannel starting points, combine content blocks with interaction elements, and publish changes without disturbing the live experience.
Manage many flows, then shape each journey visually
ChatbotX separates flow management from the builder canvas, so teams can organize a growing library of journeys while still editing each one in a focused workspace.
A structured dashboard before the canvas
The management layer is built for scale: folders group related journeys, the flow list stays searchable, and teams can control status, inbox mode, and maintenance actions before opening a single node.
Library control
Folders, search, and create actions keep large automation libraries readable.
Live operations
Status toggles, inbox visibility, and modified metadata support everyday maintenance.
Builder handoff
Open any flow and move into a zoomable drag-and-connect workspace.
Visual editing
See relationships between messages, logic, and action as a visible network.
Folders
Tet Campaign
New Customers
Post-purchase Care
Once inside the builder, teams can zoom, drag, and follow the customer path as a visible graph of messages, actions, and decision points.
Every flow begins with a starting step and a clear system structure
Flow Builder supports both omnichannel journeys and channel-specific setups when a flow depends on features that only exist on one platform.
Choose how the journey enters the system
Every flow includes a required starting node. That entry step defines whether the journey should adapt automatically across supported channels or stay dedicated to one channel when the experience depends on a channel-only component.
Omnichannel mode
Build once and let ChatbotX adapt the structure for Messenger, WhatsApp, Instagram, and other supported channels.
Channel-specific mode
Use a dedicated channel when the flow depends on channel-only interaction patterns.
Three component groups
Every journey is made of content blocks, interaction elements, and logic or system nodes.
Entry Node
Omnichannel or channel-specific
Send Message & Content Blocks
Text, media, cards, carousel, file, data collection
Interaction Elements
Buttons and quick replies that guide the next choice
Logic & System Nodes
Conditions, waits, traffic split, and silent actions
Canvas behavior
Zoom and drag to follow the journey as a visible network of nodes.
Decision points
See how messages, choices, and logic connect in one place.
Touchpoints
Track the customer path without flattening it into a checklist.
Content blocks and interaction elements shape the customer-facing layer
Inside one flow, teams can combine visible content, collect structured user data, and guide the next step through buttons or quick replies.
Display content
Use send-message blocks to assemble visible content directly inside the conversation.
Send Text
Send Image / Video
Send File
Send Card
Send Carousel
Get User Data
Ask for a specific value, pause the flow, then save the reply into the right custom field with validation.
Buttons and Quick Replies
Both tools help customers choose the next step, but they behave differently inside the conversation.
Buttons
Stay visible under a message or card and can be pressed again later.
Quick Replies
Disappear after the customer taps or sends a manual reply, which keeps the active path clean.
What interaction elements can trigger next
Send Message
Continue the current path in the same flow.
Open Website
Send the customer to a destination URL or mini-app style endpoint.
Perform Action
Run a background operation without another visible message.
Start External Flow
Jump into a reusable flow stored elsewhere.
Start External Node
Land on a specific node inside another flow.
Start Another Node
Jump to another point inside the current flow.
Content + Interaction Layer
Customer-facing blocks
Message stack
Validation-ready input
Choice layer
Guide the journey while deciding whether an option should remain visible or disappear after use.
Logic nodes, silent actions, and publishing safety complete the automation layer
Once the visible message path is built, ChatbotX handles routing, delays, data updates, integrations, and release protection through background system nodes.
Logic nodes
Condition Node
Check tags or custom fields with AND or OR logic and keep a fallback branch ready.
Smart Wait
Delay the next step by fixed time or by a saved value such as appointment timing.
Split Traffic
Divide customers across branches by percentage for structured A/B testing.
Action categories
Inbox Actions
Contact Actions
Broadcast & Email Actions
Flow Actions
Tools
Integrations
Action nodes behave like silent assistants. They update data, route conversations, or connect external systems without showing the customer another visible message.
Draft and publish safety
Automatic draft
Edits save automatically without touching the live version.
Publish
Push the latest tested version to future real-time conversations.
Revert to Published
Discard the current draft and return to the last live version when needed.
Inbox Actions
Transfer to human or bot, assign or auto-assign, archive finished conversations.
Contact Actions
Add or remove tags, set or clear fields, add notes, block or delete contacts.
Broadcast & Email
Manage subscribe or unsubscribe state for outbound care paths.
Flow Actions
Jump to another node, start an external flow, or land at a specific node elsewhere.
Tools
Get Data From JSON, Format Date, Generate Code, and Count Characters.
Integrations
Push to Google Sheets or call centralized LLM APIs as one supporting capability inside the flow.
Publish Protection
Release-safe workflow
1. Draft changes
Text edits, node updates, and connections save automatically as draft.
2. Review and test
Draft work stays separate while the live journey keeps running.
3. Publish or revert
Move the tested version live, or restore the last published version if the draft should be discarded.
Frequently
asked
questions
