postMessage events to the parent window so you can react to save, delete, and back-navigation actions.
These events are separate from the JavaScript SDK events used for public form embeds (
submit, pageChange, etc.).Message format
All editor events use this structure:Events
| Event | When it fires | Payload |
|---|---|---|
formSaved | Editor save succeeds (create or update) | { form: { id, slug, title, visibility }, isNew: boolean } |
formDeleted | Form is permanently deleted | { form: { id, slug, title, visibility } } |
navigateBack | Editor navbar back button is clicked | { from: { view, route }, to: { view, route } } |
View identifiers
Theview field in navigateBack payloads uses stable, human-readable IDs:
| Route name | view |
|---|---|
home | forms_list |
forms-create | create_form |
forms-slug-edit | edit_form |
forms-slug-show-submissions | submissions |
forms-slug-show-share | share |
forms-slug-show-integrations | integrations |
forms-slug-show-stats | stats |
forms-slug-show-summary | summary |
forms-slug-show-pdf-templates | pdf_templates |
| (unknown) | raw route name |
Parent listener example
Origin targeting
By default, messages are sent to the parent with target origin*. For stricter security, pass your CMS origin as a query parameter on the iframe URL: