How do I set up the Condition step?

What is it for?

The “Condition” step looks at variables and sends the agent down one of its paths.

Visitors don't see this step and the avatar doesn't say anything; the agent carries on without waiting for the visitor.

To add it, click “Add step” on the “Flow” tab, then click “Condition” in the “Logic” category; the step is added in the middle of the canvas. Its settings are on the “Content” tab of the step panel that opens on the right when you click the step.

This step has no “On-screen text”; instead there's a “Step note” at the bottom of the panel. The note is just for you: visitors don't see it, and it isn't spoken or translated.

In values you use variables from earlier steps, like {city}. For a field inside an answer, add the field's name after a dot: {order.status}. The “Insert variable” button in the boxes lists the variables you can use at that point. A variable that hasn't been filled yet counts as empty text.

Setting up paths

A new step opens with one path; click “Add path” for more.

1. Give the path a name (e.g. Large project). Without a name, the canvas shows a summary of the path's rule.
2. Write the rule. Each rule is one line: the value to check on the left (e.g. {budget}), the comparison button in the middle and the value to compare with on the right (a fixed value or another variable).
3. For another rule, click “And” or “Or”. Rules linked with And must all be met; with Or, either side is enough. And binds first: “A and B or C” means “(A and B) or C”. You can change the link later with the And | Or switch between the rules.
4. Pick the step the path goes to in the list under the path (it shows “No target step selected” while empty), or connect the path's handle to a step on the canvas.
5. Pick a step for “Otherwise” at the bottom too: if no path's condition is met, the flow goes there.

Paths are checked from top to bottom; the first one whose condition is met is taken and the rest aren't checked. Change the order with the arrow buttons (“Move up”, “Move down”) and remove a path with “Delete path”. If the path that's taken has no step selected, the agent ends there; it doesn't fall through to the next path.

Comparison types

The comparison button first asks for a type, then the comparison. The type decides how the values are compared:

• “Text”: “is equal to”, “is not equal to”, “contains”, “does not contain”, “starts with”, “does not start with”, “ends with”, “does not end with”. Upper/lower case, spaces at the start and end, and accents don't matter: “REFUND” equals “refund”.
• “Number”: “is equal to”, “is not equal to”, “is greater than”, “is less than”, “is greater than or equal to”, “is less than or equal to”. Formats like 1,250.50 and 1.250,50 are read too, and currency signs are ignored. If either side isn't a number, the rule isn't met.
• “Date”: “is the same day”, “is a different day”, “is after”, “is before”, “is on or after”, “is on or before”. Dates are compared by day; both 2026-12-31 and 31.12.2026 are read.
• “Yes / no”: “is true (yes)” and “is false (no)”. “yes”, “true” and “1” count as true; “no”, “false” and “0” as false.
• “List”: “contains item”, “does not contain item” and comparisons of the item count (“item count is equal to”, “item count is greater than” …). A multiple-choice answer, a tool's or action's list and an Edit List result are read as lists.

Every type also has “is empty” and “is not empty”, which need no second value. For example, the rule {coupon} “is empty” is met if the visitor didn't enter a coupon code.

Example

In a quote agent, the “Large project” path goes to a Request step with the rule {budget} · “Number” · “is greater than or equal to” · 50000. The “Nearby city” path goes to a booking form with the rules {city} “is equal to” London “Or” {city} “is equal to” Manchester. “Otherwise” is connected to a Message step saying the quote will be sent by email.

Things to watch out for

The editor flags the step when: there are no paths; a path has no rules (it's never taken); a rule is incomplete (one of its values is empty, so it's never met); a fixed value that isn't a number or date is written where one is expected; a path has no step to go to; or “Otherwise” isn't connected.

Logic steps don't wait for the visitor. If you connect them (or other steps that don't wait, such as Message, Tool Call or Integration Action) in a ring, the agent keeps going round: the editor warns “In a loop that never waits for the visitor; the flow gets stuck here.”, and in the conversation the agent ends with an error. To repeat something, use the Loop step, or put a step that waits for the visitor (Question, Selection, Form) in the ring.

Problems don't stop you saving: the agent is saved, but the incomplete step won't work as expected in the conversation. Fix the flagged steps, then try the agent with “Preview”. To find flagged steps, see the flow editor.