Add Conditionals to Agents

Last updated: April 27, 2026

Conditionals are decision points within your Agent workflow that enable different paths based on variable values.

Use a Conditional branch if an Agent must operate differently depending on an input or a value generated in a previous step. For example, you can route workflows to trigger different prompts based on specific user input.


Add a Conditional

Click the “+” icon in the Agent Editor and select “Conditional” to add a Conditional. Alternatively, you can click and drag the “Conditional” option into the workflow from the node selection menu. 

Conditionals require you to define a condition using a comparison expression (for example: equals, greater than, less than, or contains). If the condition evaluates as true, the Agent follows the True branch. If the condition does not evaluate as true, the Agent follows the Not True branch.

Each branch can contain its own sequence of steps.


Configure Conditions

When configuring a Conditional, select:

  • The variable to evaluate

  • The evaluation operator

    • Equals

    • Not Equals

    • Greater than

    • Less than

    • Greater than or Equal 

    • Less than or Equal

    • Contains

  • The value to compare it against

You can add multiple conditions to the same branch. When multiple conditions are configured, all conditions must be satisfied for the Agent to follow the True branch.

Click “+ Add Condition” to add multiple conditions to the same branch. You can add up to four conditions to a conditional branch. Multiple conditions can be combined using AND (all conditions must be true) or OR (at least one condition must be true).  

If the conditions are not satisfied, the Agent automatically follows the Not True branch.


Conditional Branch Requirements

There are several considerations to ensure an Agent executes as expected:

  • The variable used in a condition must exist. It must be created in a previous step. 

  • Each branch can contain multiple steps. 

  • Both branches must ultimately lead to an Output step to complete the Agent run.

  • The evaluation operator must align with the input variable.

    • Numerical operators only work with numeric values. For example, “Greater than” will not work on an input string such as “Best AEO Tools”.

    • String operators only work on text strings. For example, “Contains” will not work on a numeric value of 126.