Create forms and manage submissions

Define the form before adding fields #

Name the decision or workflow the response supports. Collect the minimum data needed to complete that purpose. The standard Form builder can save responses to this site's Form submissions inbox; it does not expose database mapping or email-notification destinations.

Write the success state and privacy explanation before styling. Marketing consent and sensitive personal data require deliberate retention and access rules. The current builder has no file-upload answer type, so do not promise or request attachments through this form.

Open the Form builder and choose a starting method #

1. Add or select a Form component. In Attributes, choose the first action, Form fields, to open Form builder.
2. Choose From a template for a proven structure. Current templates include Contact us, Request a quote, Newsletter signup, Support ticket, Job application, Event RSVP, Customer feedback, Book an appointment, Waitlist signup, and Lead qualification.
3. Or choose With AI, answer “What should this form ask?”, and choose Build the fields. Ctrl/Command+Enter also runs it. Generated questions use the description and a bounded amount of page context; review every result.
4. When questions already exist, choose Replace mine or Keep mine and add before applying a template or AI result. Replace mine is selected by default. Replacing with a template also updates the form name, button text, and thank-you message; appending does not. AI changes fields only.
5. For manual changes, choose Add field. A newly inserted Form starts with name, email, and message controls; there is no Blank form action. New and duplicated fields open immediately for editing.

Choose the right answer type and edit each question #

Each question is a collapsed card so a long form remains scannable. Open a card to edit Answer type, Question people see, an example answer where supported, choices, a hint below the field, Must be answered, and Half width. Use the card buttons to Move up, Move down, Duplicate, or Remove.

• A placeholder is only an example. The question label must still identify the answer.
• Enter choice options one per line. Use Label | value only when the stored value should differ from the visible label.
• Half-width fields sit beside the next field when room permits and become full width below 480 px. Labels configured Beside also stack above their controls at that width. Keep the field order logical in both layouts.
• Duplicating creates a separate answer key and opens the copy for review.
• The current builder has no file-upload answer type. Do not promise attachments or request documents through this form.

Set answer keys, validation, and conditions #

Open Rules & conditions inside a question when the defaults are not enough:

• Answer key is the stable column name used by the inbox. It follows a new question label until you edit the key yourself. Keep every collecting field's key present and unique.
• Shortest allowed, Longest allowed, and Must match this pattern expose advanced text rules. Do not rely on them without a published test: Long text currently applies required and maximum length, but not its exposed minimum or pattern.
• What to say when the answer is wrong is used by manually validated choice fields. Ordinary inputs currently surface the browser's own validation message instead of this custom copy.
• Only ask this when… watches another answer. Conditions support is, is not, has any answer, and is left empty. The picker allows any other value-collecting question, not only an earlier one. For is or is not, select or enter the answer to match.

Save form refuses an empty answer key, duplicate keys, a choice question with no choices, or a condition that waits on a removed field. Removing or renaming a watched question therefore requires reviewing dependent conditions.

Finish Form settings and inbox capture #

At the top of Form builder, complete Form settings:

• Form name is internal and labels the form in the submissions inbox.
• Button text is the visible submit action.
• After someone submits can show a Thank-you message or send the visitor to another page. Choosing the message clears any old redirect when the form is saved.
• Save answers to this site's Form submissions inbox controls capture for this form. Only the published site records submissions; using the form inside the editor never creates a lead.

The submissions inbox is the only response destination exposed by the standard Form builder. Database mapping and email notifications are not configurable in this workflow, so do not promise either as part of a form launch.

The public endpoint currently accepts at most 20 collected answers, a 16 KB payload, and 1,000 characters per value. It rate-limits repeated traffic and drops sensitive-looking field names.

Choose Save form only after reviewing fields and settings. This closes the dialog, updates the component, and requests a page save. Wait for the editor status to reach Saved.

Test from the published origin #

1. Publish only when the current site mode supports the form. The immutable release gate currently fails closed for form-containing pages.
2. Open the public hostname, not the editor preview, and submit a distinctive test value.
3. Confirm the success state is announced and keyboard focus ends somewhere sensible.
4. Verify the submission in this site's Form submissions inbox.
5. Submit invalid data, a missing required field, and the form twice. Confirm errors are understandable and duplicate behavior is acceptable.
6. Trigger every conditional branch. Hidden questions must be disabled so a required hidden answer cannot block submission or send a stale value.
7. At phone width, confirm paired fields and Beside labels stack without clipping, horizontal scrolling, or a confusing reading order.

Published controls receive accessible names from their visible questions, and the submission status is announced through a polite live region. The builder does not prevent an empty visible question, so never use placeholder text as the only label. The current builder dialog itself still lacks complete modal semantics and focus trapping; that is a product accessibility limitation, not something a page author can repair inside the form.