Post-submission actions
Control what a visitor sees and does the moment they submit a form.
The Settings step of the form wizard includes a post-submission action selector. This single choice controls every visitor's experience the moment they click Submit — from a simple thank-you to a fully embedded booking flow.
The four actions
The form resets (or shows an inline success message) and the visitor remains on the same URL. Use this for forms that expect repeated submissions, such as feedback or event check-ins.
Replaces the form with a Nomow-hosted landing page. Pick any published page from the dropdown. The swap is instant — no redirect.
Sends the visitor to any URL — your own site, a third-party confirmation page, or a Calendly link. The redirect fires immediately after the server confirms the submission.
Opens one of your Nomow booking pages — either inline, in a new tab, or as a full redirect. This is the most powerful option because name, email, and company data carry across from the form automatically.
Booking sub-panel
Choosing Open booking page reveals a sub-panel with three additional fields.
| Field | Options |
|---|---|
| Booking page | Select any of your published booking pages by slug |
| Embed mode | Inline iframe / New tab / Redirect |
| Booking domain | Use default (app.nomow.ai) or a custom domain |
Embed modes
- Inline iframe — the booking page renders inside the same iframe as the form. The visitor never navigates away. This is the recommended mode for embedded flows on third-party sites.
- New tab — opens
/book/:slugin a fresh browser tab. The original form page stays open. - Redirect — sends the visitor directly to the booking URL, replacing the form in the browser.
The form-then-booking embedded flow
When a form is embedded on a third-party page (via iframe or script) and its post-submission action is set to Open booking page in inline iframe mode, Nomow performs an iframe swap:
- The visitor fills out and submits the form.
- The form's iframe body is replaced with the booking page at
/book/:slug. - Name, email, and company values from the form are passed as query parameters (
?name=...&email=...&company=...&_d=<base64 payload>). - The booking page reads those parameters, pre-fills the corresponding fields, hides them, and shows a "Booking as [name] ([email])" banner so the visitor knows their details carried over.
- At each booking stage transition, the inner iframe posts
nm-embed-scroll-toto the parent, which recenters the visible area — so the embedded flow stays centered even inside an iframe-in-iframe structure.
Next steps
See Publishing & embedding for the embed code snippets, or configure your booking page availability in Availability and rules.
Was this article helpful?