Submit Message node reference
You can show a thank-you message after a form submission. See how to format it, insert visitor data, and choose between a message and an automatic redirect.
A Submit Message shows content in your widget after a visitor submits a form. It ends that path, so you can leave visitors with a confirmation or a link they choose to open.
When to use it
Use a message when visitors should stay on the page after submitting. For example, WorkForge (opens in a new tab) might show "Thanks! Your WorkForge guide is on its way." The form's action and connected platform must actually send the guide. Writing that message doesn't send an email.
The Message palette item adds this node inside Post-Submit Actions For This Form. You can't add it to an ordinary parent-flow path. An empty post-submit path receives a default thank-you message.
If visitors should leave the page immediately instead, use a Redirect.
Settings
The editor has one Content field, a multiline rich-text editor. A new message starts with Thank you!. Replace that text with your own confirmation.
The rich-text editor supports headings, paragraphs, bulleted lists, and numbered lists. Selecting text shows controls for bold, italic, strikethrough, underline, and links.
In a flow, the variable insertion control can add available data to your message. For example, Your planning score is {{ score.planning }} displays a calculated score, while {{ variable.last_topic }} reads a stored variable. Preview with the data present and absent so you can spot any unexplained blanks.
A message can confirm a selected topic and link to a useful page. For a WorkForge example, it could link to https://workforge.rightmessage.com/solutions.html. Use your own real destination and give visitors one clear next action.
The widget controls the message's appearance. This node has no placement, trigger, device, or dismissal settings of its own. See widget display settings for where and when the widget appears.
How visitors move through it
A message ends the post-submit path. It doesn't continue to a question or run a redirect after a delay. Nodes placed later on the same path can be unreachable, so put supported data actions before the message.
A link in the message lets the visitor choose to open a page. It isn't an automatic redirect or a continuation through later nodes. If you place a message before a redirect, the message prevents that automatic redirect.
The message itself doesn't submit the form, identify the visitor, write a custom field, or send a webhook. Those actions need to run separately. When testing a submission, check the message's text, links, and inserted data as well as any preceding actions.
Things to know
- The node has no recipient, email template, contact-field mapping, or submission-action selector. Those belong to the form and connected platform. Test email delivery before promising an email in your confirmation.
- Messages need a widget to display them, so system flows don't offer this node.
- There's no built-in countdown or continue button. Any additional question needs to come before the message.
- Text changes save as a draft. Review and publish them before expecting the new message to appear on your live website.
For help choosing what happens after submission, see form completion and redirects.