Linking Flows Together

WARNING

There is no dedicated "Go to Flow" node in OmniBots. Flow-to-flow navigation is handled through bot configuration and flow architecture rather than a specific node type.

OmniBots supports modular bot design by allowing you to organize conversation logic across multiple independent flows. Each flow is a self-contained conversation graph with its own Start node and logic.

How Flow Routing Works

Bot-Level Flow Assignment

Each bot can have multiple flows assigned to it. The bot's primary flow is the entry point for new conversations. Additional flows can be linked through the bot configuration.

Independent Flows

Independent flows are tenant-level flows (not tied to a specific bot) that can be reused across multiple bots. They are managed from the Flows section in the sidebar.

Routing Between Topics

To route a conversation to different logic paths based on user intent, use these nodes instead of a separate "go to flow" node:

• Condition -- Branch based on variable values to direct the conversation to different node paths within the same flow.
• Intent Router -- Route based on a detected intent variable, with one output handle per intent group.
• LLM Response -- Use the LLM to classify user intent and store it in a variable, then branch with a Condition node.

Modular Design Pattern

A common architecture is to use a single flow with distinct branches:

[Start] → [LLM Response: Classify Intent] → [Condition: intent]
               ├── "billing"  → [Billing branch nodes...]
               ├── "support"  → [Support branch nodes...]
               ├── "sales"    → [Sales branch nodes...]
               └── Default    → [General FAQ branch nodes...]

Each branch handles its topic independently within the same flow. Use the Group visual container to organize branches on the canvas.

imageFlow builder canvas showing a modular design pattern with a Start node leading to an intent classifier, then a Condition node branching into distinct topic groups for Billing, Support, and Sales, each visually organized using Group containers

Modular flow design pattern on canvas

Variable Scope

Session variables are shared across the entire conversation, regardless of which branch or path is being executed. Variables set early in the flow are accessible in all subsequent nodes.

TIP

If your flow is growing too large to manage on a single canvas, consider splitting logic into separate bots connected via the orchestration layer, or use Group nodes to visually organize related nodes.