Skip to main content
Branch and Add condition mean: this question owns follow-up behavior. You do not drag an If / Else card from the Logic sidebar. Stay on a normal field (Select, Multiple choice, …) and either:
  • use Branch (choice answers → show follow-ups / go to page), or
  • use Add condition (or Edit as When → Then) for the full When → Then editor under the same field
For the big picture (Branch vs Rules vs Calculated), see How logic works.

When to use Branch vs Rules

Prefer Branch for ~90% of “if they pick X, show Y / jump” cases.

Non-choice fields (Show if)

Branch is for choice / select / radio answers. On text, number, email, and other non-choice fields, use Show this field if… on the target field:
  1. Select the field that should appear conditionally.
  2. In the field chrome, click the workflow icon (Show if…).
  3. Pick the source field, operator, and value.
  4. Studio compiles a Show blocks rule (inverted attachment — logic lives as a Rules entry that reveals this field).
Need full When → Then under the same field? Click the icon again for Edit as When → Then, or use the link under the card. Switch back with Use Show if…. Selecting a field alone does not open logic — only the chrome workflow icon does.
When Company is not emptyShow blocks Invoice address
When Budget greater than or equal 1000Show + Require Phone
Same engine as Branch — only the Studio chrome differs.

Branch on a choice field

1

Select the choice field

Click the Multiple choice / Select / Radio that should own the branches.
2

Open Branch

Hover the field, then click the chrome workflow icon (Branch). Selecting the field alone does not open Branch.
3

Configure each answer

For each option: Show follow-up (pick fields) and/or Go to page.
4

Set Otherwise

Otherwise is the default path when no answer branch matches — continue to the next page, or jump elsewhere.
5

Test

Preview or use Logic → Simulator. Confirm follow-ups show/hide and jumps land correctly.
If the recipe is too complex for Branch, Studio shows the When → Then editor under the field automatically. On a Branch field you can still switch: Edit as When → Then (or the field chrome workflow icon — tooltip says Edit as When → Then while Branch is open), then Use Branch to go back. The same chrome icon is context-aware and is the only way to open under-field logic:

Advanced: When → Then under the field

1

Select the parent field

Click the field that should own the rule.
2

Open When → Then under the field

On a Branch field: chrome workflow icon (tooltip Edit as When → Then while Branch is open), or the Edit as When → Then link under Branch. On Show-if fields: the same icon toggles Show if…When → Then. On other fields: tooltip Open Rules opens Workflow → Rules.
3

Build When

Source field + operator + value; All / Any groups as needed.
4

Build Then

Common stacks: Show + Require on a follow-up; Hide when not needed; Make optional when a required field should relax.
5

Reorder and test

Multiple rules can live on one field. They run in evaluation order with all other Rules. Preview: pick Other → follow-up shows; pick a normal option → follow-up hides and clears.

Compared to Rules and Calculated


Operator & action tips

  • Open the field-type → operator matrix when an operator is missing.
  • Blank parent answers do not trigger equals or not equals — use Is empty.
  • Hide blocks clears answers.
  • Conflict chips appear when rules fight — fix before publish.
  • Deleting a follow-up field scrubs Branch / Rules references automatically.

Worked recipes

Other → specify (classic)

  1. Multiple choice includes option Other.
  2. Short text “Please specify”.
  3. On the choice: Branch → Other → Show follow-up “Please specify”.
  4. Optional: in Rules, Require that field when Other is selected.

Checkbox unlocks phone

When “Call me back” equals YesShow + Require Phone
(Add condition or Rules — same engine)

Empty company hides invoice block

When Company is emptyHide Invoice address

Common mistakes

Check Branch row for the right option, When value spelling, whether the parent is answered, and whether a later Hide overrides Show.
Did you also Require it? Is another visible required field on the visited path empty?
Hide clears answers. If you see old data, inspect Submissions after a clean fill.
Fine for testing, but move local follow-ups to Branch so Rules stays readable for routing.
Last modified on September 7, 2026