Templates & the email builder

Templates keep your content in one place so campaigns, journeys and API sends all reuse the same approved wording and design.

Creating templates

Content → Templates → New. A template belongs to a channel (email, SMS, WhatsApp, push, in-app) and supports variables in double curly braces:

Hi {{first_name}}, your order {{order_id}} ships tomorrow.

Variables resolve from the contact profile (standard fields, custom fields and computed traits) plus any per-send payload you pass in the API call. A missing variable falls back to the default you define on the template — never an embarrassing {{first_name}} in a real send.

The email builder

Email templates open in a visual builder: drag in sections (text, image, button, divider, product grid), style them, and preview on desktop and mobile widths. The builder outputs battle-tested responsive HTML — you never touch table markup. Prefer full control? Switch any template to raw HTML mode and paste your own.

Images come from the media library (Content → Media or POST /v1/media), which stores your uploads once and serves them from the platform CDN host.

Using a template

• Dashboard: pick the template inside a campaign or journey step.
• API: POST /v1/messages/send with "template_id": "tpl_…" plus a "variables": { … } object.
• Management: GET/POST/PUT /v1/templates, duplicate with POST /v1/templates/:id/duplicate.

Every send records which template version it used, so a template edit never rewrites history in message analytics.