A form collects information from visitors. It can send them to a URL, create a CMS item through a workflow, search a collection, or sign an end user in.
Last updated
A form by itself only shows fields. Its Form tab decides what happens when someone submits it.
Add a Form block. It starts with a submit button and room for fields.
Add fields from the form toolbar. The common types are:
Text
Phone
Number
Password
Date
Time
Dropdown
Checkboxes
Multiple choice
Multi-select
Select a field and open the Field tab to change its label, placeholder, type, and input name.
The label tells people what to enter. The placeholder shows an example inside the field.
A placeholder is not a label. It disappears when someone starts typing. Always use a visible label for anything important.
Good labels are short and specific: "Email address", "Order number", "Preferred date".
The input name is the key used when the form is submitted. A workflow or search form uses it to find the value.
Use short, clear names: email, name, message, phone. Avoid spaces and punctuation.
If you rename an input after connecting a workflow, update the mapping in the Form tab.
Open the Form tab and choose one of these:
Sends the form to another address. This is for a third-party form service or your own endpoint. Set the URL and choose GET or POST.
Starts a workflow when the form is submitted. The workflow must begin with a Form submission trigger. Map each workflow input to a form field.
This is the usual choice for:
Saving a contact message to a collection.
Adding a newsletter subscriber.
Creating an order request.
Sending a confirmation message and redirecting to a thank-you page.
Read Workflows for the steps.
Turns the form into a search form. The visitor's values become URL parameters, and a collection list page uses them to filter a repeater.
Choose the collection's list page as the results page. The form fields can search text or filter by a field.
Read Repeaters for the search setup.
These actions connect the form to end-user accounts. They require Users & Login to be turned on.
Read Users and login for the full setup.
The submit button sends the form. Change its label to match the action: "Send message", "Subscribe", "Create account".
Disable or remove the form while you are still building it. A live form with no action confuses visitors.
A workflow can show a success or error message when the visitor returns to the page. It can also redirect to another page, such as a thank-you page.
Keep the message short and specific. "Thanks, we will reply within one working day" is more useful than "Success".
Use the test panel in the workflow editor to run the workflow without side effects. Then submit the form on a preview page and check:
Required fields behave as expected.
The success message appears.
The new item is in the collection.
The redirect goes to the right page.
Read Workflows for the test flow.
For a contact form:
Add a form.
Add name, email, and message fields.
Add a workflow with a Form submission trigger.
Add a Create item step for a "Messages" collection.
Map the form fields to the workflow inputs.
Add a Show message step for the success case.
Bind the form to the workflow in the Form tab.
Test with a dry run, then submit a real test.
Then publish the page. Workflows are live immediately, but the form itself needs to be published with the page.
A website builder that works like a document. CMS, forms and EU hosting included.
© 2026 Remake. All rights reserved.
