Flow Builder (v8)

overview the flow builder is the visual heart of the exo chatbot platform, providing a powerful no code interface for designing and automating conversational user journeys it is a canvas based tool where you can map out every step of a conversation by creating and connecting nodes each node represents a point in the conversation and can contain various elements, such as sending a message, asking the user for information, performing a backend action, or applying conditional logic this visual approach allows you to craft everything from simple, single turn interactions to complex, branching dialogues that can integrate with apis, query databases, and execute custom code the flow builder is designed to be intuitive, enabling both technical and non technical users to build, test, and manage sophisticated chatbot logic without writing a single line of code key components of the flow builder include the canvas an infinite workspace where you arrange and connect your conversation nodes nodes the building blocks of a conversation, representing a step or a state in the user's journey elements specific items you add inside a node, categorized as bot messages, prompts, actions, and logic connectors the lines you draw between nodes to define the flow of the conversation from one step to the next ultimately, the flow builder is where the abstract concept of a user conversation is transformed into a functional, automated, and interactive experience how to use the flow builder this guide provides a detailed walkthrough of the flow builder interface and its core functionalities 2 1 accessing the flow builder to create a new flow navigate to workflow > flows and click the + create flow button to edit an existing flow from the workflow > flows page, locate the flow in the table and click the edit (pencil) icon in its actions column 2 2 the flow builder interface top navigation bar contains the back button, flow status (which indicates errors), a language switcher for multilingual bots, and the preview bot button for real time testing the canvas the main workspace where you build your conversation by adding and connecting nodes flow map a mini map in the bottom right corner that helps you navigate large, complex flows 2 3 building a conversation configuring the intent trigger (first node) every flow starts with an intent trigger node click it to configure flow name the primary phrase that triggers the conversation (e g , "check order status") training questions add alternative user phrases (e g , "track my package") select channels & category assign the flow to specificchannels and an organizational category adding steps (nodes) to the flow click the + icon on an existing node to add a new step this opens a menu with four categories of elements to add bot messages to send information to the user (text, image, carousel, etc ) prompts to get information from the user (text, quick replies, form, etc ) user input can be stored in variables connecting nodes drag the circular connector from one node to the next to define the conversation path logic nodes (like condition ) will have separate connectors for different outcomes (e g , if/else), allowing for branching paths managing nodes and elements click the three dot menu on a node to copy step , copy tree (node + all subsequent nodes), or delete step within a node, you can edit , delete , or rearrange the individual elements saving and testing the builder auto saves use the preview bot button frequently to test your logic common usecases restaurant table reservation intent trigger "book a table" prompt (form) ask for number of guests, date, and time store these in variables action (api) call the reservation system's api with the collected variables logic (condition) check the api response if successful, send a confirmation message if not, inform the user the time is unavailable customer support ticket creation intent trigger "i have a problem" prompt (quick replies) "what is this regarding? \[billing] \[technical issue]" prompt (text) "please describe your issue " store the description in a variable action (database) use insert entry to save the details to a "support tickets" table best practices keep flows focused each flow should accomplish one primary goal break complex processes into smaller, reusable flows linked with the execute flow action name nodes clearly descriptive node names (e g , "ask for email," "check api for availability") make large flows much easier to understand and debug always build failure paths when using an api or database action, always connect the failure path to a node that gives the user a helpful message use variables extensively store every piece of user input in a variable this enables personalization and allows you to pass data between steps and to external systems common mistakes creating "spaghetti" flows avoid crossing connector lines all over the canvas if a flow becomes too messy, it's a sign it should be broken into smaller, more manageable flows forgetting to store prompt responses a common error is asking the user a question with a prompt but forgetting to select a variable to store their answer in dangling nodes every node should be part of a complete path a node that isn't connected to anything is a dead end and will break the conversation not setting a default/else condition when using a condition node, always define the else path to handle any case that doesn't match your if conditions ignoring asynchronous behavior api calls can take time design your flow with "please wait" messages where necessary to manage user expectations note this flow builder is available on version 8 and onwards