Form blocks
Form blocks collect information from visitors — an email for your newsletter, a contact message, a lead's details. What people submit flows into your Leads and customer records.
The blocks
| Block | What it puts on the page |
|---|---|
FormField | One input in a form. Every field you add costs you completions — ask only for what you will use. |
FormRoot | A form. Add the fields inside it. |
NewsletterRoot | An email capture block. The simplest way to keep a visitor who is not ready to buy. |
What happens — and what doesn't
- Submissions become leads and contacts — a newsletter signup or contact form feeds your CRM, not just an inbox.
- A form is a Root holding Field blocks; you add the fields you need inside it.
- Form-input styling comes from the theme's component controls, so fields match your store's look.
- Newsletter signups can connect to your campaigns for follow-up.
Where do form submissions go?
Into your Leads and customer records. A newsletter signup or contact form feeds your CRM so you can follow up, not just an email inbox.
How do I build a form with the fields I want?
A form is a Root block that holds Field blocks. Add the fields you need inside the form, and style them via the theme's form-input controls.
What this screen looks like in every state
| State | When you'll see it | What you see, and what to do |
|---|---|---|
| Empty | You haven't created anything here yet | “No pages found” — with a shortcut to create the first one. Nothing is wrong; there's just nothing to show yet. |
| Loading | The screen is fetching your data | A skeleton in the shape of the finished page. It should be brief — if it persists, the load has failed rather than stalled. |
| Error | The data couldn't be loaded | A message with a retry. Retry first: most of these are a dropped request, not a broken store. If it repeats, the outage is upstream and reloading won't help. |
| No access | Your role doesn't include this screen | A permission notice instead of the page. An owner or admin can grant access under Settings → Team. |
When something goes wrong
These are the messages this screen can show you, and what each one means.
| If you see | What to do |
|---|---|
| "…" is reserved for a built-in store page (like cart or checkout). Choose a different slug. | Retry the action. If it keeps happening, contact support with what you were doing. |
| Cannot delete the shop page. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |
| Delete the product to remove this page. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |
| Page title is required. | A required field is blank. Fill it in and save again. |
| This page is protected and cannot be deleted. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |