Write once. Reuse across every send.
One template powers your transactional messages, campaigns, and automations. Merge fields, versioning, and previews keep content reliable as your sending scales.
- Across campaigns & API
- SharedAcross campaigns & API
- Full history
- VersionedFull history
- With real subscribers
- PreviewWith real subscribers
- Per workspace
- ScopedPer workspace
Content sprawl is the silent killer of outbound quality.
When every campaign, sequence, and transactional email lives in a different place, updates get missed, variants diverge, and brand consistency erodes.
One source of truth
Every send references the same template object — no more three slightly-different versions of the same welcome email.
Update once, propagate everywhere
Edit the template; every campaign and automation that points to it picks up the new version on next send.
Never lose an old version
Full version history with diffs. Roll back if a change breaks rendering or merges.
Merge fields, safe defaults, deterministic rendering.
Variables resolve against subscriber fields and per-send payloads. Fail-fast or fall-back behavior is a per-template setting.
<h1>Hi {{ subscriber.first_name | default: "there" }},</h1>
<p>Welcome to {{ workspace.name }}.</p>
<p>Your account is ready at
<a href="{{ payload.login_url }}">{{ payload.login_url }}</a>.
</p>
<p>You're receiving this because you signed up
at {{ subscriber.source | default: "our site" }}.</p>Hi Priya,
Welcome to Acme Outbound.
Your account is ready at https://app.acme.co/login.
You're receiving this because you signed up at /pricing.
Everything you need to scale content without chaos.
HTML + plain text
Synced HTML and plain text versions, both versioned, both rendered per send.
Merge fields & defaults
Handlebars-style variables with per-field fallback values to prevent broken sends.
Per-workspace libraries
Each workspace owns its templates — perfect for agencies and multi-brand teams.
API-first
Reference templates by ID or alias in the API, automations, and campaigns.
Compliance helpers
Built-in unsubscribe and footer tokens ensure every send stays compliant.
Spam & render checks
Automated checks for link health, image weight, and common spam triggers before publish.
The questions teams ask about content.
Stop copy-pasting your email content.
Centralize templates, version every change, and let every campaign and automation inherit them.