Conditional logic & multi-step

Show fields only when they are relevant, make them required only when they matter, and split long applications into pages.

Two features that turn a long form into a short one. Both live in the flow builder.

Conditions exist only in the flow builder. Opening a form with conditions in the basic editor and saving will drop them.

Conditional logic

A field can depend on the answer to an earlier field:

• Show if — the field only appears when the condition is met.

• Require if — the field is always visible, but only mandatory when the condition is met.

An example

Are you a reseller? → Yes / No

• Reseller certificate (file upload) — show if "Are you a reseller?" is Yes

• Tax exemption number — show if "Are you a reseller?" is Yes, require if the same

Non-resellers never see either field. Resellers cannot submit without both.

Setting one up

1. Select the field that should be conditional.

2. Open its condition settings.

3. Choose the controlling field, and the value that triggers it.

4. Pick show if or require if.

The canvas draws conditions as dashed lines between fields, with a legend explaining the colours. On a form with several conditions, that picture is the fastest way to check you have wired it the way you meant to.

Chained conditions

Conditions can chain: field C depends on B, which depends on A. If A hides B, then C hides too — visibility flows through the chain rather than leaving orphaned fields visible.

That is usually what you want, but it makes long chains hard to reason about. Test them in the live preview.

Multi-step forms

Insert a page break to split the form into steps. Everything after a page break, up to the next one, becomes a page. Applicants move through with Back and Next.

To reorder, drag fields across the page break — step membership follows field order.

When to split

Worth it above roughly eight fields, or when the form has distinct phases:

1. About you — name, email, phone

2. Your business — company, website, years trading, territory

3. Compliance — tax number, reseller certificate upload

4. Confirm — consent, anything else

A four-page form with four fields per page reads as far less work than a sixteen-field page, even though it is the same questions.

Combining with conditions

The two work together, and this is where the builder earns its keep: an entire compliance step can be conditional on business type, so resellers get four pages and everyone else gets three.

Testing

Open the live preview and walk every branch:

• Answer Yes to each controlling question, then No. Confirm the right fields appear and disappear.

• Check require if actually blocks submission when it should.

• Click through every step forwards and backwards.

• On chained conditions, confirm hiding the top of the chain hides everything below it.

Then submit a real application from your storefront before announcing the form. The preview renders the form; a real submission also exercises validation, file uploads and your approval automations.