Logic
Conditions and actions: show or hide questions, jump, calculate, require, redirect.
Logic lets a form react to answers. A rule has a condition (or a group of conditions combined with and/or) and one or more actions.
Conditions
Conditions compare an answer, a variable, a value from the form link, or a respondent attribute against a value. You can nest groups, and use an expression for more complex checks.
Actions
Action | What it does |
|---|---|
Show / hide a question | Reveal or conceal a field. |
Show / hide a section | The same for a whole section. |
Jump to a section or question | Skip ahead based on an answer. |
End the form | Finish early, optionally on a chosen ending screen. |
Redirect | Send the respondent to a URL after submission. |
Set a variable | Store a computed value for later rules and piping. |
Set a message | Change a message shown to the respondent. |
Require a field | Make a question required only in some cases. |
Set a value | Fill a field from an expression. |
Disable / enable a field | Lock a field or make it editable again. |
Set an input mask | Change a field's mask on the fly. |
Hide the submit button | Hold back submission until a condition is met. |
Trigger a workflow | Start an automation. |
Variables and piping
Variables hold numbers or text computed from answers (for example a score). Pipe answers and variables into question text and messages with curly-brace references. System values such as the respondent's device, country, locale and date are available too.
Validation rules
Besides logic, fields have validation: minimum and maximum length, pattern, minimum and maximum value, and minimum and maximum selections.
Tips
Keep rules readable: prefer several small rules over one large one.
Use logic tests to check each branch before you publish.
Advanced logic is part of paid plans; see Billing basics.