# 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.

Available on the Grow, Scale, and Pro plans.

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](https://workforge.rightmessage.com) playbook signup as an example.

You'll need project edit access. [Connect your email platform](https://rightmessage.com/help/how-integrations-work) 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

1. Open **Forms** under **Convert** and choose **New form**.
2. Choose **Blank**.
3. Under **What should it collect?**, keep **Email address** selected. It's required. Select **First name** if you need it.
4. Enter a **Form name**, such as `WorkForge playbook signup`. Only your team sees it.
5. 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.

![Live preview of the opt-in form before a visitor enters an email address](https://rightmessage.com/help/screens/builders-form-live-preview.light.webp)

Form text can use the same [personalized phrases as offers](https://rightmessage.com/help/offer-content-reference). 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.

1. Open **Fields** and choose **Add field**.
2. Choose a question type, or reuse a question under **From your question library**.
3. Select the field to edit its label, placeholder, required state, or width where supported.
4. Set the question's sync mapping, or use **Save answers to** for a native field.
5. Arrange the fields in the order you'd like people to fill them in.

![Form Fields panel with email and submit fields and the Add field button highlighted](https://rightmessage.com/help/screens/builders-form-fields.light.webp)

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.

![Does Work With Team field inspector showing its current label, mapping and field options](https://rightmessage.com/help/screens/builders-form-question-field.light.webp)

Email and Submit stay on every form. The [form fields reference](https://rightmessage.com/help/form-fields-reference) covers field types, layout, copying forms, and managing them later.

## Choose where submissions go

1. Open **Actions**.
2. Choose your **Action**.
3. Select its destinations, such as your list or tags.
4. Fix any warning that says submissions can't be sent.

![Form Actions editor showing the configured lead capture action](https://rightmessage.com/help/screens/builders-form-actions.light.webp)

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](https://rightmessage.com/help/form-actions-reference) covers the available actions, webhook plan requirements, and endpoint settings.

## Add the form to your flow

1. Open the flow where you'd like the form to appear and add a **Form** node.
2. Choose the form you just created.
3. 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](https://rightmessage.com/help/flow-node-offer-form) 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](https://rightmessage.com/help/best-practices-for-testing) to repeat the path. The debugger simulates contact updates, so you'll check actual delivery after publishing.

![Opt-in form with alex@example.com and Yes, I manage or work with others selected](https://rightmessage.com/help/screens/builders-form-populated.light.webp)

When you're happy with it, [publish your changes](https://rightmessage.com/help/publishing-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](https://rightmessage.com/help/widget-and-offer-results).