Create a form and choose its submission action
You'll build a form that collects visitors' details, sends them to your email platform, and gives people a confirmation after they submit.
A form lets visitors join your list or ask for something, then sends their details to your email platform or webhook endpoint. We'll use a WorkForge (opens in a new tab) playbook signup as an example.
You'll need project edit access. Connect your email platform so the form can add people to the right list, apply tags, or start your follow-up. You can build the form before creating the flow and widget that will show it.
Create your form
- Open Forms under Convert and choose New form.
- Choose Blank.
- Under What should it collect?, keep Email address selected. It's required. Select First name if you need it.
- Enter a Form name, such as
WorkForge playbook signup. Only your team sees it. - Choose Create form.
Your form opens on Content.
Tell visitors what they're signing up for
Write a Headline that explains what they'll get, add an optional Description, and set the Button text. Add an image if your widget's theme displays one, then check the preview.
Form text can use the same personalized phrases as offers. If you're editing a form you already use, check Uses in the full editor first. Your changes apply to every flow that uses it.
Ask for the details you need
Fields let you collect more than an email address. Mapping each answer to your email platform makes it available for your follow-up.
- Open Fields and choose Add field.
- Choose a question type, or reuse a question under From your question library.
- Select the field to edit its label, placeholder, required state, or width where supported.
- Set the question's sync mapping, or use Save answers to for a native field.
- Arrange the fields in the order you'd like people to fill them in.
A new question type creates a shared library question. Reusing a question keeps its existing settings. An input question without a sync mapping can still collect answers, but those answers won't populate an email-platform field.
Email and Submit stay on every form. The form fields reference covers field types, layout, copying forms, and managing them later.
Choose where submissions go
- Open Actions.
- Choose your Action.
- Select its destinations, such as your list or tags.
- Fix any warning that says submissions can't be sent.
Your connected platform determines which actions you can choose. Create or update a contact doesn't need a destination list. Other actions can need one or more IDs.
If you're sending to your own endpoint instead, a webhook can work without an email-platform connection. The form actions reference covers the available actions, webhook plan requirements, and endpoint settings.
Add the form to your flow
- Open the flow where you'd like the form to appear and add a Form node.
- Choose the form you just created.
- Set up Post-Submit Actions For This Form on the canvas. Add a confirmation message or a redirect to the real page you'd like people to reach.
A form ends the ordinary path through its flow. After submission, it follows its own post-submit path instead of ordinary nodes placed after the form. The Offer and Form node reference explains the available post-submit actions.
Check it on your website
With the project's snippet installed, choose Preview on your site in the bottom bar. Your draft opens on your real website with the debugger docked at the bottom.
Check the fields and confirmation for both new visitors and visitors RightMessage already knows. Follow testing your changes to repeat the path. The debugger simulates contact updates, so you'll check actual delivery after publishing.
When you're happy with it, publish your changes. Submit the form on your normal website using a test contact you control, then check their details in your email platform or webhook receiver.
When the visitor sees the right confirmation and the destination receives their details, your form is working. Next, see how often visitors submit it.