Conditions

A condition makes everything inside it depend on a rule. When the rule is true, everything inside is active — fields are shown, variables are calculated, navigation fires, and field changes apply. When false, everything inside is skipped entirely.

This means conditions aren’t just for showing and hiding fields. You can put any logic block inside a condition to make it depend on answers: a variable that only updates when a certain option is picked, a page redirect that only fires for specific respondents, or a change-field block that makes a question required in certain scenarios.

Adding a condition

Type /condition (also matches /if, /when) and press Enter. The condition appears as a bordered region in the editor with a label at the top like IF @role is "Manager".

Setting the rule

Click the condition label to open the editor. Pick a field, choose an operator, and enter a value. Add more rows with + Add condition and join them with AND/OR.

Supported operators

Operators are shown in plain language:

Builder labelSyntaxMeaning
is=Equals (case-insensitive for text)
is not!=Does not equal
is greater than>Greater than
is less than<Less than
is at least>=Greater than or equal
is at most<=Less than or equal
containsCONTAINSText includes a substring, or multi-select includes all given options
does not containNOT CONTAINSText does not include the substring
contains any ofCONTAINS_ANYAt least one of the given options is selected
contains none ofCONTAINS_NONENone of the given options are selected
contains exactlyCONTAINS_EXACTLYExactly these options are selected and no others
is empty= EMPTYField has no value
is not empty!= EMPTYField has a value

Not all operators appear for every field type — the dropdown only shows the operators that apply to the selected field.

Multiple rows can be joined with AND (all must be true) or OR (any must be true).

Nesting

Conditions can go inside other conditions. Inner conditions only evaluate when their outer condition is true.

What conditions can wrap

Everything except page breaks: fields, text, images, variables, repeats, go-to-page, open-website, change-field blocks, and other conditions. Page breaks are always top-level.

Tips

  • The builder handles the vast majority of real-world conditions. For more complex logic, create a variable with the full formula syntax and reference it in the condition
  • Click the chevron on the condition label to collapse it and reduce visual clutter
  • Fields inside a false condition are excluded from required validation, so respondents won’t get stuck
  • Combine conditions with variables to build scoring patterns — set a score to 0, then conditionally increment it