> ## Documentation Index
> Fetch the complete documentation index at: https://docs.theomnibot.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Building and Managing Conversation Flows in ChatbotX

> Learn how to design, manage, and publish automated conversation journeys using ChatbotX's visual Flow Builder drag-and-drop canvas.

Flows are the control center of ChatbotX. Instead of writing complex code, you use the visual **Flow Builder** drag-and-drop interface to design automated conversation journeys for your customers — organizing logic as intuitively as mapping ideas on a mind map. Every message, decision point, and background action lives inside a Flow, giving you complete visibility into every step of the customer experience.

## Flow Management Interface

When you open **Flows** from the left navigation menu, you land in the management dashboard. This interface is designed with a clear hierarchy so you can handle a large number of Flows in a structured and readable way.

| Element                | Description                                                                                                                                                         |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Folders**            | A tree-style storage structure. Use **+ Create Folder** to group related Flows into one category, such as `Tet Campaign`, `New Customers`, or `Post-purchase Care`. |
| **Flows List**         | Displays every Flow inside the selected folder, along with a search bar and the blue **+ Create Flow** button in the top-right corner.                              |
| **Status**             | A toggle that lets you disable a Flow immediately without deleting it.                                                                                              |
| **Inbox**              | A status mode that controls whether the Flow appears inside the conversation Inbox for your team.                                                                   |
| **Modified & Actions** | Shows the last time you edited the Flow, with an action menu to Rename, Duplicate, or Delete it.                                                                    |

## Flow Builder Interface

**Flow Builder** is an open canvas workspace where every message, data-processing action, or logic condition is packaged as a **Node**. Rather than forcing you through a flat list view, Flow Builder gives you a visual network-style layout with modern drag-and-connect behavior.

* Zoom in and out to see the full Flow clearly at any scale.
* Visualize the relationship between messages, actions, and decision points at a glance.
* Follow the customer journey and touchpoints more easily throughout your funnel.

## Starting Step

Every Flow must include a **Starting Step** — the green starting block that defines how the Flow begins. The Starting Step gives you two setup modes:

<AccordionGroup>
  <Accordion title="Omnichannel">
    Build one Flow once, and ChatbotX automatically adapts the content structure for each supported channel — Messenger, WhatsApp, Instagram, and more. This is the recommended default for most use cases.
  </Accordion>

  <Accordion title="Channel-Specific">
    Choose a single platform when your Flow depends on a feature that only exists on that channel, such as a WhatsApp List Menu. The Flow will only run on the chosen channel.
  </Accordion>
</AccordionGroup>

## Components That Make Up a Flow

To build a complete Flow, you connect Nodes and Steps drawn from three main groups of blocks:

### Send Message & Content Blocks

Blocks that display content directly on the customer's device — text, images, Carousel cards, attached files, and more. Full configuration details are covered in the Content Blocks guide.

### Interaction Elements

**Buttons** and **Quick Replies** that help customers interact, make choices, and move to the next step in the journey.

### Logic & System Nodes

Background blocks that handle routing and data without displaying any message to the customer:

| Node           | Purpose                                                                                                                        |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Condition**  | Evaluates contact data (Tags, Custom Fields, channel, purchase history) and routes each customer to the correct branch.        |
| **Actions**    | Performs silent system tasks — applying Tags, updating Custom Fields, assigning conversations, calling APIs, and more.         |
| **Smart Wait** | Pauses the Flow for a fixed duration before continuing, regardless of whether the customer replies.                            |
| **Follow Up**  | Pauses the Flow and cancels the next step if the customer replies before the timer expires. Ideal for re-engagement reminders. |
| **A/B Split**  | Distributes traffic across multiple branches for split testing.                                                                |

## Version Management

ChatbotX includes a built-in protection layer so you can safely iterate without affecting live conversations.

<Steps>
  <Step title="Automatic Draft Saving">
    Every text edit, block update, and connection change is saved automatically as a **Draft**. At this stage, your edits do not affect the live customer experience.
  </Step>

  <Step title="Publish When Ready">
    After you finish testing the Flow, click the green **Publish** button in the top-right corner. Only the published version runs in real-time conversations.
  </Step>

  <Step title="Revert to Published">
    If your draft introduces a mistake, use **Revert to Published** to restore the last published version. This action discards all current draft changes and brings Flow Builder back to the latest live state.
  </Step>
</Steps>

<Warning>
  Reverting to the published version permanently discards all unsaved draft changes. Make sure you have reviewed your draft before using this option.
</Warning>

<Tip>
  Use **Folders** to keep Flows organized by campaign or business function. A clean workspace makes it much easier for your team to locate and update the right Flow quickly.
</Tip>
