Email templates with variables
Build reusable email templates once and let variables like {{contact.firstName}} personalize every send — from the inbox composer or an automation.
Templates save your team from retyping the same email dozens of times a day. A template is written once — subject, HTML body, variables — and then reused everywhere: reps insert it in the inbox composer with Use template, and automations send it for you when a trigger fires.
Templates live under Settings → Templates. Every template has a Type; for email you'll use:
- Email — an HTML message sent through your connected mailbox, with a Subject line.
- Universal — one template that carries both an HTML form for email and a plain-text form for chat channels; the picker substitutes whichever fits the sending surface.
Variables
Personalization runs on {{...}} merge tags. Type a variable anywhere in the subject or body — the editor hint says it directly: use {{variable_name}} for substitutions. Built-in variables come grouped by record:
| Group | Examples |
|---|---|
| Contact | {{contact.firstName}}, {{contact.fullName}}, {{contact.email}}, {{contact.phone}} |
| Deal | {{deal.name}}, {{deal.amount}}, {{deal.currency}}, {{deal.stage}}, {{deal.pipeline}} |
| Company | {{company.name}} |
When you insert a template in the composer, each tag is resolved from the current deal, contact, and company. A tag that cannot be resolved stays in the draft verbatim, so the gap is visible — but check the draft before sending: at send time the server empties any leftover tags instead of blocking the send, so an unfilled gap goes out as "Hi ,". The safety net is per-variable defaults entered in the editor's right rail — a default also acts as a fallback at send time. The preview panel substitutes exactly those defaults (its hint says so: "Variables interpolated from defaults shown in the right rail"); a variable without a default renders as the raw tag.
Beyond the body
- Name — the template's display name; the slug automations reference is derived from it.
- Plain-text fallback — optional text version for mail clients that don't render HTML.
- Custom signature — an HTML signature appended after the body; leave it empty to fall back to the mailbox's own signature.
- Attachments — files stored on the template travel with sends from the inbox composer; the automation send-email action does not attach them.
- Status — Active templates appear in pickers; an Inactive template is hidden from selection when sending but kept for later. Templates whose variables are unsupported are flagged under Issues so you can fix them.
Drag templates in the list to reorder them — the picker shows them in the same order, so put the most used ones on top.
For text templates aimed at Telegram and WhatsApp, see Message templates for chat channels.
Was this article helpful?