The Condition step is a decision node that routes execution down different paths based on conditions you define. Branches are evaluated top-to-bottom and the first matching branch runs while the others are skipped. An optional else branch catches anything that doesn't match.

• Route leads to different follow-up steps based on their score or status
• Send different email templates depending on a form response
• Skip expensive processing steps when input data doesn't meet criteria
• Build approval workflows where accepted and rejected items take separate paths
• Gate a section of your workflow so it only runs when a condition is true

Connect the Condition step to two or more downstream steps with outgoing edges. Each edge becomes a branch in the step's configuration panel. Branches are evaluated in order from top to bottom using the conditions you define. The first branch whose condition evaluates to true is taken and its downstream steps execute normally. All other branches are skipped, and their downstream steps are cascade-skipped as well. If no branch matches and there is no else branch (a branch with no condition), all downstream paths are skipped. You can reorder branches with the up/down arrows to control evaluation priority. Conditions reference fields from upstream steps, using the same operators available in edge conditions (equals, contains, greater than, etc.).

What's the difference between Condition and Filter?

Condition routes the workflow down different paths based on data. Filter removes items from a list. Use Condition for branching logic, Filter for narrowing down arrays.

Can I have more than two branches?

Yes. Add additional outgoing edges and each becomes its own branch. Branches are evaluated top to bottom, and the first match wins.

What happens if no condition matches?

All downstream paths are skipped unless you add an else branch (one with no condition). The else branch catches anything not matched by earlier branches.