How Branch Conditions Work

Branch nodes route the workflow along Yes or No based on conditions evaluated against values submitted in upstream Action steps.

Anatomy of a condition

Each condition has three parts:

1. Field — a form field from any previous Action step
2. Operator — the comparison to apply
3. Value — the target to compare against

Example: Field: Decision Operator: equals Value: Approve

If the upstream assignee selected "Approve", the condition is true → Yes path. Otherwise → No path.

Available operators

Operator	Works with	Description
equals	Text, Dropdown, Radio, Number, Date	Exact match
not equals	Text, Dropdown, Radio, Number, Date	Not an exact match
greater than	Number, Date	Strictly greater
less than	Number, Date	Strictly less
greater than or equal	Number, Date	≥
less than or equal	Number, Date	≤
contains	Text, Checkbox	Substring or selected option

Multiple conditions (AND logic)

All conditions must be true for the Yes path. Any false condition → No path.

This is AND logic. For OR logic, chain multiple Branch nodes in sequence.

Example:

Decision   equals        Approve
Amount     less than     10000

Only approved requests under 10,000 take Yes. Approved requests ≥ 10,000 take No.

Which fields are available?

A Branch node can evaluate fields from any Action step that comes before it in the canvas. Fields from steps after the branch are not available.

Empty field behaviour

If an evaluated field is blank (optional and not filled), the condition evaluates to false → No path.

→ Fields used in branch conditions should almost always be marked Required.

Testing before publishing

1. Click the Branch node
2. Review the condition list — verify each field, operator, and value
3. Ensure both Yes and No handles are connected

All handles must be connected to publish.

See also

• How to Configure Branch Conditions
• Understanding the Four Step Types
• Form Data in Branch Conditions