A workflow is a set of steps that runs automatically. It can save a form submission, send a message, create a CMS item, or run on a schedule.
Last updated
Think of it as a small automation: when this happens, do that.
A workflow has one trigger:
Form submission runs when a visitor submits a connected form.
Schedule runs hourly, daily, weekly, or monthly, at the time you choose.
Item created, Item updated, and Item deleted run when a collection item changes.
Manual run runs only when you press play in the editor.
After the trigger, add steps. Each step connects to the next.
Condition branches on a value. It has true and false outputs.
Transform computes values that later steps can use.
Find items reads items from a collection.
Create item adds an item to a collection.
Update item changes an existing item.
Show message displays a success or error message when the visitor returns to the page.
Redirect sends the visitor to another page.
Send email sends an email through the configured provider.
Log writes a value to the server log.
Sign up, Log in, Log out, and Social sign-in connect to end-user accounts.
Steps that can fail have success and error outputs. Connect the error output to a message or a log so a failure does not disappear silently.
Many step fields accept a value from earlier in the run. The picker offers:
Values submitted by the form, such as input.email.
Values from a previous step, such as steps.<step id>.name.
Values you computed in a Transform step.
The current user, such as currentUser.email.
Date helpers such as =now() and =today().
Start typing in a value field to see the available options. The expression editor also has a function list.
The Test panel runs the workflow with values you provide.
Dry run does not write to the CMS or send anything. It records what each step would do.
Run for real writes to the CMS. The CMS is the same data the live site uses, so use this only when you mean it.
Use a dry run while building. Use a real run once, with a test item, before connecting a public form.
Create a workflow with a Form submission trigger.
Add the steps.
Add the inputs the form should send. For example, email, name, and message.
Go to the form on the page, open the Form tab, and choose Workflow.
Map each workflow input to a form field.
If the form changes, check the mapping again. A renamed field leaves an input unmapped.
Workflows do not wait for a site publish. Saving a workflow applies it to the live site right away.
That is convenient, but it also means a half-finished automation can run. Test it before you connect a public form.
Workflows are included on every plan.
A workflow can only read and write CMS collections. It cannot call other web services.
The Send email step needs transactional email to be configured (RESEND_API_KEY and EMAIL_FROM). Without it, no email is sent and only a single warning is logged.
There is no saved run history. Test runs return a trace, but production runs leave only logs.
A workflow is a sequence of connected steps, not a general-purpose program. It has no loops or custom code.
Items created by a workflow are published and count toward your CMS item limit.
For a contact form:
Create a Messages collection with name, email, message, and received date.
Create a workflow with a Form submission trigger.
Add inputs for name, email, and message.
Add a Create item step for Messages and map the inputs.
Add a Show message step with a success message.
Add an error branch with a friendly failure message.
Run a dry test.
Connect the form to the workflow.
Submit a real test and check the item.
Read Forms for the page side, and Items and publishing for the CMS side.
A website builder that works like a document. CMS, forms and EU hosting included.
© 2026 Remake. All rights reserved.
