Forms: conditional logic

Conditional logic lets one form behave like several. Questions appear only when they apply, whole steps are skipped when they don't, the respondent lands on a thank-you message that fits their answers, and the alert for a new response goes to the people who need to act on it. All four use the same condition builder, so once you have written one condition you know how to write the rest.

#Writing a condition

A condition has three parts: a question from the form, a comparison, and a value. "Budget is at least 5000" or "Reason for contact is Sales".

• For a dropdown, radio, checkbox, chips or multiple-choice question, the value is picked from that question's own options, so a typo can't silently break the rule.
• A yes/no question offers Yes and No; a terms or consent box offers Checked and Not checked.
• Every other question takes a value you type.

Choose Add another condition to combine several, then set Match to All conditions (every one must be true) or Any condition (one is enough).

#Comparisons

• is / is not — the answer is exactly the value, or anything else.
• contains / does not contain — the value appears anywhere in the answer, ignoring capitals.
• is empty / is not empty — whether the question was answered at all. These take no value.
• is greater than, is at least, is less than, is at most — offered on number, decimal, currency, slider, rating, NPS and calculated questions. Currency symbols and thousands separators are ignored, so "₹12,500" compares as 12500.

#Showing a question only when it applies

Click any question on the canvas and open Conditional logic in its properties. With no condition it is always shown; choose Add condition to show it only when the conditions match.

• A hidden question is never required, so it can't block the submit button.
• Its answer is never sent. A respondent who answered it and then changed an earlier answer leaves nothing behind from the branch they backed out of.
• Hiding a column layout hides everything inside it.
• A question hidden by its own condition can't keep a later question visible — its answer no longer counts.

#Skipping a step

On a multi-step form, click a page break and open Step logic. A condition there decides whether the step after that break is shown. Only questions that come before the break can be used, since nothing after it has been answered yet.

• Next and Back jump straight past a skipped step.
• The progress indicator counts only the steps this respondent will actually see, so "Step 2 of 3" stays honest.
• Required questions on a skipped step don't block anything, and their answers are not sent.

#A different ending for different answers

Open After submission on the icon rail. Below the default message or redirect, Endings by answer holds as many alternative endings as you need. Each one has a When (its conditions) and a Then: a message shown in place of the form, or a redirect to a URL.

• Endings are checked from the top, and the first one that matches is used — put the most specific ones first.
• When none match, the default above is used.
• A matching ending wins over the default completely: an ending with a message is shown even if the default is set to redirect.

Typical uses: send qualified leads straight to a booking page while everyone else sees "we'll be in touch", or thank a detractor on an NPS form differently from a promoter.

#Sending the alert to the right people

Open Email Notifications, switch to Notify me, and use Route by answer. Each route has conditions and a list of addresses; when a response matches, the alert also goes to those addresses.

• Routes add to the main recipients rather than replacing them. To send sales enquiries only to sales and support requests only to support, leave the main To empty and use two routes.
• Someone who appears in several matching routes still gets one email.
• Routes only send while Notify me is switched on, and like every notification email they need an email app connected — see Notifications & integrations.

#Example: a B2B enquiry form

• Company size is shown only when Enquiry type is Sales.
• The Budget step is skipped unless Enquiry type is Sales.
• An ending for "Enquiry type is Sales" and "Budget is at least 50000" redirects to your calendar booking page.
• A route for "Enquiry type is Support" alerts support@yourcompany.com.

#Good to know

• Conditions point at a question, not its label, so renaming a question never breaks them.
• If you delete a question that a condition uses, open that condition and pick a new question — until you do, it compares against an empty answer.
• Test the paths in Preview before publishing: nothing is saved and no payment is taken there.