Flow Builder
Branches and conditions
Split the dialogue with deterministic conditions or LLM prompts.
The Branch node allows the flow to split. Each path has a condition or acts as a fallback.
Condition types
| Type | When to use |
|---|---|
| Deterministic | Compare variables with exact operators. |
| LLM prompt | Let the model decide whether the path applies based on the call context. |
Deterministic condition
Each path can have one or more rules:
variable: the variable name.operator:equals,not_equals,contains,greater_than,less_than,is_empty,is_not_empty,is_true,is_false.value: the value to compare (not required foris_empty,is_not_empty,is_true,is_false).
When there are multiple rules, set matchMode:
any: one rule being true is enough.all: all rules must be true.
LLM prompt condition
Write a natural language instruction. The model evaluates whether the path should be followed. Example:
"The customer said they want to talk to a human or the issue is urgent."
Fallback path
Each branch node can have at most one Otherwise path. It is taken when none of the other conditions apply.
Validation
The Flow Builder requires:
- At least one path with a condition.
- At most one fallback.
- Each path must point to an existing target.
Use deterministic conditions for exact logic (price, menu option) and LLM prompts for open intents.