# Condition Block Not all conversation flows follow a linear path. Often, different paths need to be taken based on specific criteria, such as the information provided by the user. This is where the Condition Block comes into play. The Condition Block uses conditional logic to **determine how the conversation should proceed based on certain conditions being met**. By combining logical operators and variables, this block enables specific parts of the conversation flow to be activated, allowing for **dynamic responses tailored to user inputs**. This helps in creating intelligent and adaptable conversational paths that are based on real-time data or information shared during the conversation. {% hint style="info" %} The functionality of this block is driven by [Variables](/getting-started/workspace/variables.md): check out the article for detailed guidance. {% endhint %}

## How It Works The Condition Block functions based on variables, checking if certain conditions are met before proceeding to the next step in the conversation. To define a condition, the block evaluates three key components: 1. **Variable**: The data or input being assessed (e.g., user preferences, choices, or responses). 2. **Operator**: The logical operator used to evaluate the condition (e.g., equals, greater than, etc.). Operators can be unary (e.g., IS NULL) or involve a condition value. 3. **Condition Value**: The value being compared against (e.g., a specific user input or a predefined variable value). The available operators depend on the selected variable type: once you choose a specific variable, only the corresponding operators will appear in the dropdown. This results in different sets of operators being available depending on the variable type: * **Text**

* **Number**

* **Boolean**

* **Date/Time**

* **Agent, workflow or variable**

### Multiple conditions A single Condition Block can evaluate multiple conditions. These are processed **sequentially from top to bottom**. When a condition is true, the corresponding action is executed, and subsequent conditions are skipped. It is important to **arrange the conditions in the desired order**, as the block will execute the first satisfied condition.

The Condition Block also provides flexibility to combine conditions using logical operators: * **AND / NOT AND**: All conditions must (or must not) be true. * **OR / NOT OR**: At least one condition must (or must not) be true. {% hint style="info" %} When resetting or initializing variables, it's best practice to explicitly set them to **`null`** OR `empty`, ensuring a clean starting state with no residual data from previous interactions. {% endhint %} When conditions are satisfied, the conversation proceeds to the next set of blocks based on the actions defined for each condition. ## Best Practices ### Using the “Else” Condition In many scenarios, you might want to define an action for when none of the conditions are met. This is where the **“Else”** condition comes in. By using the **True** **variable** (a system variable that always evaluates to true), you can set up a default **action that is triggered if no other conditions are satisfied**. This ensures that there is always a fallback behavior. {% hint style="info" %} Since conditions are evaluated in order and only the first matching one is executed, it's best to add an "Else" condition at the end, so that it works as a fallback action for when none of the previous conditions are met. {% endhint %} For example: * If condition1 is true → proceed to action1. * If condition2 is true → proceed to action2. * Else (if no conditions are true) → proceed to a fallback action.

### Using Counters and Variables for Dynamic Actions Another powerful use of the Condition Block is combining it with variables like **counters** to dynamically control the flow. For example, if a user asks for support, the Condition Block can check a counter variable (e.g., counter = 1) and provide an initial response. If the user asks for help again, the counter increases, and the conversation is routed to a human operator using the Handover Block. 1. If assistance\_requested = true and counter = 1 → Virtual assistant responds. Add a [Set Value](/getting-started/agents-workflows-and-triggers/blocks/logic-blocks/set-values-block.md) block and set counter = 2. 2. If assistance\_requested = true and counter = 2 → Handover to a human operator with an Handover block.

## Action Management Once a condition is met, the associated action is executed, guiding the user through the conversation flow in a structured manner. **If the condition is not met, the block is ignored**, and the conversation continues as usual. ### Adding Blocks to the Condition In the Condition Block, you can **add any type of action block after each condition check**. For example, you can use the Message Block to send a message or the Reroute Block to redirect the conversation. However, you cannot add another Condition Block within a Condition Block. ## Use Case Examples #### Customer Support Personalization A support bot can use the Condition Block to offer personalized responses based on the user’s account type: * If user\_type = VIP → Provide priority support. * If user\_type = Regular → Offer standard support options. #### Product Recommendations A bot can suggest different products based on the user’s preferences: * If category\_interest = Technology → Show the latest tech gadgets. * If category\_interest = Fashion → Suggest new fashion collections. #### Dynamic Job Suggestions An HR chatbot can suggest job offers based on the candidate’s experience: * If years\_experience > 5 → Recommend senior-level positions. * If years\_experience <= 5 → Suggest entry-level roles. ## A Concrete Example Let’s take a simple example to understand how the Condition Block works: We want the assistant to address users by their name, but only ask for it once. Here's how to set it up: 1. Create a name variable (text type) to store the user’s name. Initially, the name variable will be empty (null) - this should be defined with a [Set Values](/getting-started/agents-workflows-and-triggers/blocks/logic-blocks/set-values-block.md) block at the beginning of the workflow. 2. Drag the Condition Block into the workflow and define the condition: If name is null.\ If true, ask the user for their name using the [Capture Block](/getting-started/agents-workflows-and-triggers/blocks/logic-blocks/capture-block.md) and store it in the name variable.\ After that, send a welcome message using the [Message Block](/getting-started/agents-workflows-and-triggers/blocks/message-blocks.md). 3. Add another condition to check if the user already provided their name (condition: name is not null). If true, send a "Welcome back" message without asking for their name again. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.indigo.ai/getting-started/agents-workflows-and-triggers/blocks/logic-blocks/condition-block.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.