Templates & the email builder

Templates keep your content in one place so campaigns and journeys 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). 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: templates render when a campaign is launched — POST /v1/campaigns with "template_id": "tpl_…". The single-message endpoint POST /v1/messages/send does not accept a template id; pass the finished content directly (message, plus subject and htmlmessage for email).
• Management: GET/POST /v1/templates, PUT /v1/templates/:id, duplicate with POST /v1/templates/:id/duplicate — these require a dashboard session (a JWT from POST /v1/auth/login), not an API key.

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