Condition
Create branches and route execution down different paths.
The Condition node evaluates the data it received and routes execution down one path. It is the only node with multiple outputs on the canvas, one per branch.
It handles the "if the customer asked for a refund, go this way; otherwise, go that way" case.
How evaluation happens
- The node evaluates the condition groups from top to bottom.
- The first true group determines the path taken.
- Evaluation stops there. The other branches don't run.
The order of the groups decides the result. A broad condition placed at the top catches cases that a more specific condition further down will never get to evaluate.
In practice, this means writing the most restrictive conditions first and leaving the most generic one for last.
Build the branches
Each output of the node on the canvas corresponds to a condition group. Connect each one to the part of the flow that should run in that case.
Parallel branches don't see each other. To bring the results together afterwards, use an Aggregation node.
The default case
Always have a branch for whatever didn't match any condition. Without it, unexpected input makes the flow end without going down any path, and the result comes out empty with no visible error.
Next steps
- Bring the branches together in Aggregation.
- See which branch was taken in Runs.