How Form Data Flows to Branch Conditions

Data submitted in one step can drive routing decisions in a downstream Branch node. This article explains how it works, what is accessible, and how to design for it.

The data flow model

When an assignee submits an Action step, all field values are stored. Any Branch node downstream can evaluate those values.

Trigger → [Action A: fields 1,2,3] → [Action B: fields 4,5] → Branch

The Branch can evaluate fields 1–5 from both Actions.

Selecting a field in the condition editor

1. Click the Branch node
2. Click Add condition
3. In the Field dropdown, fields are grouped by step name
4. Select the field to evaluate

Only upstream fields are shown — fields from steps after the branch are not available.

What field types can be evaluated?

Field type	Branch?	Best operator
Text	✅	equals, contains
Textarea	❌	—
Number	✅	equals, >, <, >=, <=
Dropdown	✅	equals, not equals
Radio	✅	equals
Checkbox	✅	contains
File	❌	—
Date	✅	equals, >, <

Multi-step example

Trigger
  → Submit request    [Vendor, Amount, Justification]
  → Manager review    [Decision (Radio), Approved amount (Number)]
  → Branch            [Decision equals Approve AND Approved amount >= 10000]
  → Yes: CFO approval
  → No:  Finance processing

When values are unavailable

A condition evaluates to false if:

• The field was optional and left blank
• The field's step was skipped by a prior branch path

Always mark fields used in branch conditions as Required.

Designing with branching in mind

Plan conditions first. Decide what question the branch answers, then add exactly the fields needed.

Name fields clearly. "Decision" must make clear what values mean (Approve / Reject). Ambiguous labels lead to misconfigured conditions.

Test every path. After publishing, trigger the flow and submit each step with values that cover all branch outcomes.

See also

• How Branch Conditions Work
• Required vs Optional Form Fields
• How to Configure Branch Conditions