Notification Templates
Notification templates are configured by the administrator in the Notifications section (/notification-templates, menu item System → Notifications). A template describes the subject and body of an email, which is then used in business processes and automations.
Template list
The template table shows: ID, Name, Code, Email Subject, and actions (edit, duplicate, delete). The Create button opens the form for a new template.
Creating and editing a template
- On the Notifications page, click Create (or open an existing template to edit it)
- Fill in the fields
- Set up the subject and body of the email
- Save
Template fields
| Field | Description |
|---|---|
| Friendly Name | A human-readable name for the template, e.g. "Ticket created" |
| Unique Code | A unique technical identifier for the template; generated automatically from the name (transliteration), but can be set manually. Once the template is created, the code cannot be changed |
| Email Subject | The email subject text; supports variables |
| HTML Body | The email content — edited in the visual editor |
The template code is the value used to call the template from automations and business processes (see below).
Email body editor
The email body is edited in an editor with three modes:
| Mode | Purpose |
|---|---|
| Visual | A visual WYSIWYG editor (text formatting, lists, links, images, tables) |
| HTML | Editing the email's raw HTML source |
| Preview | Preview the email with test data and send a test email |
Images inserted in Visual mode (via clipboard, drag-and-drop, or the file picker) are automatically uploaded to the server, so they remain available after the email is sent to recipients.
Switching from HTML mode to Visual only edits the email content — the <head>/<style> block in the source HTML is discarded in the process, so for emails with custom styles it's better to work in HTML mode.
Inserting variables
The subject and body use syntax (or with spaces). Both the subject field and the body editor have an + Insert variable dropdown for inserting a variable at the cursor position without typing the syntax by hand.
The list of suggested variables is built from:
- A set of commonly used variables:
id,name,title,status,task_name,entity.number,date - Variables that already appear in the subject or body (if they were typed in manually)
The exact set of available values depends on what the calling automation or process step passes in — the system doesn't restrict the template to a fixed list of fields.
Testing a template
In Preview mode you can:
- Provide test data in JSON format (fields are substituted in place of variables)
- View the subject and body with the values filled in
- Enter an email address and click Send test email — a real email with the test data will be sent
Where templates are used
A template isn't tied to an event directly on its own page — it has no "trigger" field. The binding happens where the template is applied:
- The "Notification" business process step — in the process designer the node holds a list of delivery channels: in-app push and any configured outgoing channel (email, telegram, SMS, webhook, broker). Each row has its own recipients (a user, a role, a process variable, or an entity field) and its own message — a ready-made template by code or free text with variables; a row without its own message sends the node's shared message
- Automation scripts — the template is called by code via
$api->sendEmail('template_code', recipient, variables)
This way, the same template can be reused across different processes and automations, simply by referencing its code.
Channels
Templates in this section produce email messages. For in-app push notifications and Telegram, the text is either also set via a template (where the process step supports it) or as free text with variables directly in the step's settings. For a general overview of channels and how users enable them in their profile, see Notification Channels.