What this form does
This surface is used to create a new email template or edit an existing one.
Operators use it to maintain:
- the internal template label
- subject text per language
- HTML body per language
- template type and its available variables
- test delivery before trusting a change
Create vs edit
Create
The create flow defines the template label, type, subject, and HTML body. It can also receive a notificationId from the route query when the template is being linked from a notification workflow.
Edit
The edit flow first loads the stored template, then lets the operator:
- change subject per language
- change HTML body per language
- insert AI-assisted content into the current language body
- translate body and subject into configured languages
- send a test email
- save the updated template
How preview works
The page editor renders the current HTML body with dynamic-value substitution in the browser. This helps operators review layout and placeholders, but it is still not the same thing as a delivered message.
Important actions
Create / Save: persists the new template or the selected language's edited subject/bodyTranslate: fills translated body and subject values for the saved template using the configured translation flowSend test email: sends the current edited body and subject to the address entered in the modalAI insert: inserts generated body content into the editor; it still needs Save to persistCancel: returns to the list without submitting current form changes
Known caveats
Send test emailexists only on the edit flow because it depends on the stored template context.Translateexists only on the edit flow. It can update multiple language values for the saved template.- Save and Send test email are disabled when the current language body is in an unsupported editor format, to avoid overwriting stored HTML unexpectedly.
- AI insert changes the draft editor value only. Operators still need to review and save.
notificationIdandnotificationActivecan be linked through the same email-template save/update route, so email and notification semantics meet on one record.