Offer and Form node reference
You can collect visitor details with a form or recommend a page with an offer. See your content options and what happens after a click or submission.
A Form node collects information from your visitor. An Offer / Promo node shows a link or call to action. Both use a reusable form or offer, so you can share the same content across flows.
When to use it
Use a form when you want visitors to submit their details. Use an offer when you want them to click through to a page. Put any questions or conditions that decide what to show before the form or offer.
These nodes need a widget or another supported display context. System flows can't use them.
Settings
A new node gives you four ways to choose its content. The wording depends on whether you're adding a form or an offer.
| If you'd like to… | Form option | Offer option |
|---|---|---|
| Create new content and attach it to this node | Create a new form | Create a new offer / promo |
| Reuse shared content | Use an existing form | Use an existing offer / promo |
| Make an independent copy and attach it to this node | Duplicate an existing form | Duplicate an existing offer / promo |
| Generate a new draft from a prompt | Generate a form using AI | Generate a offer / promo using AI |
The existing-content chooser lets you filter by name and keeps forms separate from link offers. AI generation opens a prompt with a Generate action. Review the draft in the editor before publishing. If generation reports an error, check whether a usable draft was created.
Once you've selected a form or offer, the node opens its editor:
- Forms have Content, Fields, and Actions.
- Offers use Content for text, the destination, and images.
- Open full editor ↗ opens the full-page controls. Results, the uses list, and A/B testing aren't available in the embedded drawer.
Shared content and eligibility
The form or offer's Enabled setting affects whether flows can use it. Conditions and routers before the node decide which visitors reach it. Personalization inside the form or offer changes its wording or image for an answer. It doesn't create another flow branch.
Editing shared content changes every place that uses it. Duplicate it when you need independent content for a new flow. Removing a node from one flow doesn't mean you should delete the underlying form or offer from your project.
How visitors move through it
Offers
An offer shows its content and link. When a visitor clicks, RightMessage records the acceptance and follows the configured destination and open behavior. Reaching the offer alone doesn't count as a click.
An offer ends the display path. It isn't a pause before more questions, so put qualification questions and conditions before it.
Forms
A form validates its fields before submitting. Email is required. Linked questions and supported native fields can have their own validation too. Invalid values prevent submission.
The selected form action sends the submission to its supported email-platform destination or queues a webhook. A provider failure can show a submission error instead of completing the form. Without the required integration, the form can't write to that contact record.
The canvas has a separate Post-Submit Actions For This Form path beneath the form. It can run conditions and actions, show a Submit Message, or redirect the visitor. Its insertion controls exclude questions, forms, offers, and Exit Flow nodes. Submitting the form doesn't continue through ordinary nodes placed after it in the parent flow.
Submitted question answers update locally before post-submit conditions check them. A message ends the path, so a redirect placed after it won't run immediately. Choose what you want visitors to see after submitting and test that exact path.
Things to know
A preview lets you check content and layout. The authorized debugger can simulate integration writes instead of sending them. To check that your provider receives a submission, use a controlled normal-browser submission and inspect the contact record.
If nothing reaches the destination, check Actions, required destination IDs, field mappings, integration permissions, and the provider's record. Webhook submission metrics don't confirm delivery to the receiving endpoint.
For the content editors, see create a form or create an offer. Form submission actions covers the available destinations. Draft changes need to be published before they appear on your live website.