Logic

overview logic elements are the decision making components of the flow builder they allow you to create dynamic, intelligent, and personalized conversational paths by directing the user's journey based on specific criteria while other elements send messages or perform actions, logic elements control the flow itself, determining which step comes next these elements are essential for building chatbots that can adapt to different situations, user inputs, and contexts instead of following a single, linear path, a conversation can branch into multiple directions, creating a more responsive and human like interaction the exo chatbot platform provides two primary logic elements condition this acts as an "if/else" statement for your conversation it evaluates the value of a variable and directs the user down different paths depending on whether the condition is met channel filter this allows you to tailor the conversational experience for different communication channels (e g , web, whatsapp, facebook) you can create unique branches to leverage the specific capabilities of each platform by mastering logic elements, you move from building simple, static bots to creating sophisticated, context aware virtual assistants how to use logic logic elements are added inside a node to create branching points in your conversation 2 1 adding a logic element on the flow builder canvas, click the + icon on a node where you want the decision to be made from the element menu, select the logic category choose either condition or channel filter 2 2 configuration details for each logic type condition the condition element creates if and else output connectors on your node, allowing you to build branching paths if condition select variable choose the variable you want to evaluate from the dropdown list select operator choose the comparison operator (e g , equal to, greater than, contains, is not empty) enter value enter the static value or select another variable {} to compare against adding more conditions you can create more complex logic by clicking + add additional condition to create nested and/or statements click + add another condition to create else if branches, allowing for multiple possible outcomes connecting paths drag the connector from the if branch to the node that should execute when the condition is true drag the connector from the else branch to the node that should execute when the condition is false you must always connect the else path channel filter the channel filter element creates a unique output connector for each channel or group of channels you define if condition the first branch is created by default click the dropdown and select one or more channels (e g , check the box for web) elseif condition click + add another condition to create a new branch select one or more different channels for this branch (e g , check the box for whatsapp) connecting paths connect each channel specific branch to the node that should execute for that channel the else branch will execute for any channel that you have not explicitly defined a path for it is crucial to connect this path as a fallback common use cases loan eligibility check (condition) an api action checks a user's credit score and stores it in a {credit score} variable a condition node checks if {credit score} is greater than 700 the if path leads to a message "congratulations, you are pre approved!" the else path leads to a message "we need a bit more information to process your application " omnichannel product display (channel filter) a user asks to see product categories a channel filter node directs the flow the web and facebook branch connects to a node with a rich carousel message, which is highly visual the whatsapp branch connects to a node with a whatsapp list prompt, which is native to that platform the else branch (for sms, etc ) connects to a simple text message listing the categories best practices always define a fallback for both condition and channel filter, always connect the else path this prevents your user from getting stuck if their situation doesn't match any of your specific branches keep conditions simple if you find yourself creating a condition node with many nested and/or statements, consider breaking the logic into multiple, sequential condition nodes this makes the flow easier to read and debug common mistakes not handling all channels when using channel filter, if you only define paths for web and whatsapp but forget the else path, a user on facebook messenger might hit a dead end comparing the wrong data types trying to use a "greater than" operator on a text variable (e g , if {user name} is greater than 100) will not work as expected ensure your variable types and operators match