Conditional Logic Setup

Conditional Logic Setup

Conditional logic allows fields to appear or disappear based on other field values. This powerful feature lets you create dynamic, context-aware forms that adapt to user input.

How It Works
  1. Enable Conditional Logic - Toggle "Conditional Logic" on for any field you want to show/hide conditionally

  2. Select the Trigger Field - Choose which field's value will control visibility (type the exact field label)

  3. Choose an Operator - Select how the trigger field's value should be evaluated

  4. Set the Condition Value - Specify the value(s) that will trigger the field to appear

Available Operators
"is"

The field appears when the trigger field's value exactly matches the condition value (case-insensitive).

Example: Show "Company Name" field when "Account Type" is "Business"

"is not"

The field appears when the trigger field's value does NOT match the condition value.

Example: Show "Student ID" field when "Account Type" is not "Corporate"

"is empty"

The field appears when the trigger field is empty or not filled.

Example: Show "Alternative Email" field when "Primary Email" is empty

"is not empty"

The field appears when the trigger field has any value (is filled).

Example: Show "Additional Comments" field when "Feedback Type" is not empty

"is one of"

The field appears when the trigger field's value matches any of the specified values. Use comma-separated values.

Example: Show "Shipping Address" field when "Delivery Method" is one of "Express, Standard, Overnight"

"is not one of"

The field appears when the trigger field's value does NOT match any of the specified values. Use comma-separated values.

Example: Show "International Details" field when "Country" is not one of "USA, Canada, Mexico"

Setting Up Conditional Logic

Step-by-Step Guide
  1. Select the field you want to make conditional (the field that will show/hide)

  2. Enable "Conditional Logic" toggle

  3. Enter the trigger field label in "If Field..." - must match exactly (case-insensitive)

  4. Choose an operator from the dropdown

  5. Enter the condition value - for "is one of" and "is not one of", use comma-separated values

Important Notes
  • Exact Label Matching: The trigger field label must match exactly (case-insensitive). Use the exact label text from your form fields.

  • Field Order Matters: The trigger field must appear before the conditional field in your form

  • Real-time Updates: Fields show/hide immediately as users interact with the form

  • Required Fields: If a required field is hidden by conditional logic, it won't block form submission

Example Use Cases
Business vs Personal Forms
  • Show "Company Name" field only when "Account Type" is "Business"

  • Show "Personal ID" field only when "Account Type" is "Personal"

Multi-Step Forms
  • Show "Shipping Address" only when "Delivery Required" checkbox is checked

  • Display "Additional Notes" when "Special Requests" is not empty

Dynamic Questionnaires
  • Show "Technical Details" when "Product Category" is one of "Software, Hardware, Electronics"

  • Display "Event Details" when "Inquiry Type" is "Event Planning"

File Upload Conditions
  • Show "Resume Upload" only when "Application Type" is "Job Application"

  • Display "Document Upload" when "Documentation Required" is checked

Nested Conditions

You can create chains of conditional fields:

  • Field A controls Field B

  • Field B controls Field C

  • This creates a cascading form experience

Best Practices
Planning Your Logic
  1. Map your flow - Sketch out when each field should appear before building

  2. Start simple - Begin with basic conditions and add complexity gradually

  3. Test thoroughly - Test all possible paths users might take

  4. Consider edge cases - What happens if users change their answers?

Field Configuration
  1. Clear labels - Use descriptive, unique field labels for easier conditional setup

  2. Logical order - Place trigger fields before conditional fields

  3. Avoid circular dependencies - Don't create fields that depend on each other

  4. Group related fields - Keep conditional fields near their triggers

User Experience
  1. Smooth transitions - Fields appear/disappear instantly for better UX

  2. Clear relationships - Make it obvious why fields appear

  3. Don't hide required fields - Avoid making required fields conditional

  4. Provide context - Use labels and placeholders to guide users

Testing Checklist
  • Test each conditional path

  • Verify fields appear/disappear correctly

  • Check with empty values

  • Test with multiple values (for "is one of")

  • Verify required field validation works

  • Test form submission with conditional fields hidden

  • Check on different devices/browsers

Common Patterns
Show/Hide Based on Selection

Pattern: Show additional fields when a specific option is selected

  • Use "is" operator with Select or Radio fields

  • Example: Show "Company Details" when "Account Type" is "Business"

Multiple Choice Conditions

Pattern: Show field for multiple possible values

  • Use "is one of" operator

  • Example: Show "Shipping Options" when "Country" is one of "USA, Canada, UK"

Empty/Not Empty Patterns

Pattern: Show alternative fields when primary field is empty

  • Use "is empty" or "is not empty" operators

  • Example: Show "Alternative Contact" when "Primary Contact" is empty

Checkbox-Based Conditions

Pattern: Show fields when checkboxes are checked

  • Use "is" operator with checkbox values (true/false or checked/unchecked)

  • Example: Show "Newsletter Preferences" when "Subscribe to Newsletter" is checked

Troubleshooting Conditional Logic

Field Not Appearing

Check:

  • Trigger field label matches exactly (case-insensitive)

  • Condition value matches trigger field's value format

  • Operator is appropriate for the field type

  • Trigger field appears before conditional field in form order

Field Not Hiding

Check:

  • Conditional logic is enabled

  • Condition value doesn't match current trigger field value

  • No conflicting conditions

  • Form data has been updated

Multiple Values Not Working

For "is one of" and "is not one of":

  • Use comma-separated values: "Value1, Value2, Value3"

  • No spaces after commas (or consistent spacing)

  • Values match exactly (case-insensitive)

  • Check for extra spaces or special characters

Advanced Tips
  1. Cascading Conditions: Create multi-level conditional logic where one conditional field triggers another

  2. Default Values: Use default values in trigger fields to pre-show conditional fields

  3. Validation: Remember that hidden required fields won't block submission

  4. Performance: Conditional logic updates in real-time without page refresh

  5. Accessibility: Ensure conditional fields are accessible to screen readers

Create a free website with Framer, the website builder loved by startups, designers and agencies.