Set up conditional logic in forms and surveys

Conditional logic makes a form or survey react to answers: show or hide fields, redirect to a URL, display a custom message, disqualify a lead, or jump between survey slides. In the form or survey builder, click Conditional Logic in the top bar to add rules.

How conditional logic works

A rule watches a form field or survey slide and acts when the answer matches a condition you define. Every rule is built from three parts: Select Field (the form field or slide), Select Field State (the condition, such as "is equal to" or "is empty"), and Provide a Value (the matching text, number, or date). Some operators need no value, like "is empty" or "is checked".

Within a rule, connect conditions with AND or OR. Each rule uses one connector type only — you cannot mix AND and OR in the same rule. Multiple rules can exist in the same form, and each works independently.

Benefits of conditional logic

Conditional logic shortens the form for each person and improves the accuracy of what you collect.

• Users see fewer questions.

• Forms are faster and easier to complete.

• Irrelevant responses are prevented, so data quality improves.

• The experience is more personalized for each respondent.

Set up a rule

Open the form or survey in its builder, then add conditions and choose the action that runs when they match.

1. Click Conditional Logic in the top bar.

2. Click Add New Condition.

3. Choose an action. The logic builder opens for that action.

4. Use Select Field to choose the form field or slide the rule watches.

5. Use Select Field State to pick the condition, such as "is equal to" or "is empty".

6. Use Provide a Value to enter the matching value — text, a number, or a date. Some operators need no value, such as "is empty" or "is checked".

7. Add more conditions to the rule if needed and connect them with AND or OR.

8. Click Save when all required inputs are valid. The system checks for missing values and prevents loops automatically before the button activates.

Available actions

Four actions are available, and each one runs when its rule matches.

• Redirect to URL — send users to a specific webpage after submission. The URL must be valid.

• Display Custom Message — show a personalized message based on answers, written in a rich-text editor.

• Disqualify Lead — automatically reject unqualified submissions. When the rule matches, the submission stops.

• Show/Hide Fields — dynamically control which fields appear or hide. Choose Hide, Show, Hide Multiple, or Show Multiple.

Branching examples

The most common use of conditional logic is showing or hiding fields based on a previous answer. If someone answers "Are you attending the banquet?" with Yes, show the meal selection; with No, hide it. The same pattern creates different paths through one form:

• Membership applications — when the applicant chooses Individual Member, Student Member, or Organization Member, show the questions that apply to that membership type.

• Event registration — show meal preferences for in-person attendance and hide them for virtual attendance.

• Sponsorship forms — reveal different benefits, questions, or add-on options based on the sponsorship level selected.

Branching lets one form handle multiple scenarios without separate forms for each option.

Supported fields

Personal Info and Form fields, plus the Text, HTML, Image, and Payment elements, can be used in conditional logic.

Calendar fields are not supported.

Operators by field type

Each field type supports a specific set of operators, chosen in Select Field State.

Survey branching with Jump To

Jump To is a survey-only action that sends respondents to a target slide or question based on how they answer.

Base the rule on a field or slide, then choose the slide or question to jump to. The rule is evaluated when the user clicks Next. If multiple Jump To rules match, the first one runs.

The builder prevents loops automatically — both self-loops and slide-to-slide cycles — and shows an error message if one is detected.

How rules are evaluated

All conditions execute in top-down order, and each action type handles multiple matches differently.

• For Redirect to URL, Display Custom Message, and Disqualify Lead, only the first matching rule runs.

• For Show/Hide Fields, later matching rules override earlier ones.

Conditional logic in calendar booking forms

Conditional logic also applies when a custom form is used inside a supported calendar booking flow.

Show/Hide logic updates fields dynamically as the user answers. Disqualify Lead is checked before the appointment is booked: a disqualified lead does not create an appointment, and no payment is collected.

Redirects and custom messages can be used as part of the booking outcome. If the calendar confirmation page is set to Use custom form rules, the form's redirect or custom message is shown after submission; if the form has neither, the booking uses the default confirmation page.

This behavior covers supported calendar booking flows; it does not cover Services (v2) and Rentals.

Tips

Keep these behavior rules in mind as you build.

• For multi-select fields, "is equal to {Option}" checks whether that option is selected.

• Text logic ignores case and extra spaces.

• Dates use the account's timezone.

• Between is inclusive for number and date ranges.

• The Radio Other option appears only when enabled for that field.

• Date presets such as Today or This Week are available.

• Always preview the form or survey to verify rule behavior.

After a submission, you can start automations from the submitted answers with the Form Submitted and Survey Submitted workflow triggers.

Test every path

Before publishing, walk through the form multiple times with different answers to confirm every branch works.

• Correct fields appear for each response.

• Irrelevant fields stay hidden.

• Required fields work — and required fields that should only appear in some branches don't block others.

• Users can complete every possible path successfully.

Testing matters most for longer forms with several branching scenarios.

Best practices

Keep your logic as simple as possible, and ask whether each condition makes the form easier to complete.

• Start with the simplest questions first.

• Group related questions together.

• Make sure required fields only appear when they apply.

• Keep branching easy to follow for future administrators.

Common mistakes

• Creating unnecessary complexity.

• Forgetting to test every branch.

• Making hidden fields required.

• Building multiple conditions when one would accomplish the same result.

• Creating several different forms when one well-designed form would be easier to maintain.