Show, hide, or require fields conditionally

Conditional logic lets one answer change another field’s state. Use it to remove irrelevant questions, not to conceal information a visitor needs before deciding to submit.

Build the controlling answer

Create the controlling field first. Choice fields work well because their option values are predictable. Keep each option value stable after conditions exist.

Example:

• Label: “Customer type”
• Name: customer_type
• Options: “Individual” and “Business”

Then create the dependent “Company name” field.

Configure a condition

1. Open the form under Forms → All Forms.
2. Select the dependent field in Builder.
3. Open Properties → Conditional Logic.
4. Enable Enable Conditional Logic.
5. Choose an Action:
   • Show If
   • Hide If
   • Require If
6. Under Rules, choose the controlling Field, an Operator, and the comparison Value.
7. Use Add Condition for another rule in the same group.
8. Select AND (all must be true) or OR (any can be true).
9. Use Add Group only when the branch genuinely needs nested logic.
10. Save the form.

Available operators include equality, containment, list membership, numeric comparison, checked state, and empty or non-empty state.

What happens to hidden values

POM Forms evaluates visibility before processing. Values and uploads belonging to hidden fields are excluded from storage, email, webhooks, and post creation.

This prevents a previously entered answer from being delivered after its branch becomes inactive. It also means an automation must not depend on a field that can be hidden for the submitted path.

Test the branch

1. Select the answer that reveals the field.
2. Confirm Require If blocks progress when the visible field is empty.
3. Enter a value.
4. Change the controlling answer so the field is hidden.
5. Submit and confirm the hidden value is absent from every destination.
6. Return to the original answer and verify the field state again.
7. Repeat on every form step where the condition can change.

If a hidden field blocks submission, inspect both its normal Required setting and its conditional action. Reduce the rule to one condition, verify it, then rebuild any nested groups.

Notification routes use related Send If and Do Not Send If conditions. Configure those in Email actions.