An E-mail Template is a reusable message body with merge tokens. Once defined, a template can be referenced from any feature that sends mail — UIVs, Tasks, Carts, Password Resets, custom callbacks. Centralising message bodies as templates means you can refine your wording once and have every feature benefit, without hunting through PHP code.
Anatomy of a template
Every template has:
- Name — internal identifier, also shown in dropdowns when picking a template.
- Subject — the email subject line, supports merge tokens.
- Body — the message body, in HTML, supports merge tokens. The platform automatically generates a plain-text version from the HTML if you don't supply one explicitly.
- From Address (optional override) — which E-mail Account sends this template by default. Leave blank to use the sending feature's default.
- Reply-To (optional override) — set a reply-to header on outbound messages.
- Attachments (optional) — files that should always be attached to messages sent with this template.
Merge tokens
Tokens in the template body are substituted at send time with values from the relevant row. The standard tokens:
##AMDATA_fieldname##— any field on the row.##AMDATA_ID##— the row's ID (useful for reference numbers, URLs).##SITE_URL##— the platform's base URL.##SITE_NAME##— the configured website title.##RECIPIENT_EMAIL##— the email address the message is being sent to.##RECIPIENT_NAME##— the recipient's name (if known from their user account).
Feature-specific tokens add to the standard set. UIVs add ##REFNUMBER##, ##STAGENAME##, ##REQUESTURL##. Password resets add ##RESETURL##, ##EXPIRESIN##. Carts add ##ORDERTOTAL##, ##LINEITEMS##. See each feature's documentation for the specific tokens.
Where templates live
Architect Panel → E-mail Templates. The list shows every template with name, subject preview, and a count of how many features reference it.
Three real-world template patterns
Pattern 1: Simple transactional
One template per type of transactional email — Password Reset, Welcome, Order Confirmation. Each has a friendly subject, branded body, and clear next-step call-to-action.
Pattern 2: Per-tenant branded
For multi-tenant SaaS, each tenant can have their own version of a base template (e.g. Confirmation Email). The Conditional Form logic on the template picks the right variant based on the recipient's tenant.
Pattern 3: Heavily-templated multi-language
For multi-language apps, one template per language per email type. So "Password Reset (English)", "Password Reset (French)", "Password Reset (German)". The platform picks based on the recipient's language preference.