Building a form

Drag the Form widget onto any page (it drops into a Container like every other widget). Its Content tab has four groups, in order: the Form Fields repeater, Save Submission to Database, Confirmations, and Behavior — this article walks through each.

Adding and configuring fields

1. 1In the Form Fields repeater, click Add Field.
2. 2Set Field Type first — the rest of the settings shown below it change to match (a Rating field shows a max-rating setting; a Range Slider shows min/max/step; and so on). See "Field types reference" for the full list.
3. 3Set the Label — this is the question text visitors see. The field's internal name (used everywhere you'd reference it — conditional logic, expressions, email merge tags, workflow steps) is generated automatically from the Label by slugifying it, e.g. "What's your budget?" becomes what_s_your_budget. Renaming the Label later keeps regenerating the name automatically, right up until you've referenced that field elsewhere — at that point, treat the Label as fixed to avoid breaking an existing reference.
4. 4Toggle Required and Read Only as needed, and add a Description for helper text shown under the label.
5. 5Switch to the field's Conditional Logic tab to make it show only when earlier answers match a rule — see "Conditional logic."

Splitting a form into pages

There's no single "multi-step" switch — instead, open any field's Advanced tab and turn on Start a New Page Here. Every field marked this way begins a new page; everything above it (down to the previous page break, or the top of the form) is the page before it.

• Behavior → Progress Bar (multi-page forms) — Off, Top, Bottom, or Top & Bottom.
• Behavior → Auto-advance to Next Page — jumps to the next page automatically once every question on the current page is answered, instead of waiting for a Next click.
• Behavior → Validation Mode — On Next Page/Submit (default), On Value Change (instant, as the visitor types), or On Submit Only (no per-page checks at all).

Saving submissions

Save Submission to Database is on by default and writes every entry to Craftor → Entries, where you can view, edit, export, or delete submissions individually or in bulk. Its own description points at the real mechanism for anything beyond storage: "For email, webhooks, Mailchimp, Slack automation use Craftor → Workflows" — see "Email notifications" and "Workflows & automations." Turning this off doesn't disable notifications or workflows; it only stops writing a row to the Entries table, useful for a form you never intend to review manually.

Confirmations

The "On Submit, Show" repeater controls what a visitor sees immediately after submitting — a Message shown in place of the form, or a Redirect to another URL. Multiple confirmations can coexist, each gated by its own "Only Show If" condition; the first one (top to bottom) whose condition matches wins, so put your specific branches above a single catch-all entry with no condition left at the bottom. See "Conditional logic" for how to branch this by answer.