Skip to content
Sendix
TemplatesPreview, publish, and reuse production content

Versioned email templates for production content

Create reusable email content with sample variables, render checks, publish history, and references your API, broadcasts, and automations can share.

Create a templateView render docs
  • Draft and published versions
  • Variable preview data
  • Render endpoint
  • Shared content references
template workspace
controlled beta
template.htmlreceipt_v3
<h1>Hi {{first_name}}</h1>
<p>Your receipt {{order.id}} is ready.</p>
<a href="{{receipt_url}}">
  View receipt
</a>
DraftPreviewPublish
Rendered previewv7
Hi Taylor
View receipt
Sample data
{ "first_name": "Taylor",
  "order": { "id": "4081" } }
Content flow

Move a template from draft to production reference deliberately.

Templates are production dependencies. Sendix keeps authoring, preview data, published versions, and send references in one flow.

01
Draft

Author content

Create reusable templates with HTML, subject, preview text, metadata, and named variables.

02
Preview

Preview variables

Render realistic sample data before an API worker, broadcast, or automation references the content.

03
Version

Publish a version

Promote the checked template so production sends reference a known version instead of an unreviewed draft.

04
Send

Reference from sends

Use templates from Email API, broadcasts, and automations while keeping delivery logs tied to content.

Render path

Preview content before it reaches a queue.

The render path lets teams inspect the subject and HTML generated from variables before a template powers transactional, lifecycle, or campaign email.

Open template editor
EventStatus
draft.savedreceipt_v3ready
preview.renderedsample orderchecked
version.publishedv7active
api.referencedPOST /v1/emailsqueued
Template surface

Content controls that belong next to delivery controls.

Reusable content is easier to operate when edits, previews, versions, and sends share one message history.

Version history

Keep a record of what changed before a template powers production receipts, notices, or campaigns.

Variable previews

Use sample JSON to catch missing data and layout mistakes before a worker calls the template.

Render endpoint

Render a template with caller-supplied variables when your product needs a preflight result.

Shared content layer

Transactional sends, lifecycle flows, and broadcasts can reuse the same content primitives.

Safer content changes

Duplicate, preview, and publish templates so content edits do not silently change production sends.

Use cases

Templates are strongest when content is reused across send paths.

The same template can become a stable contract between product, lifecycle, and operations work.

Receipts and invoices

Keep financial templates versioned and previewed before checkout workers call them.

Lifecycle messages

Reuse welcome, trial, reactivation, and onboarding content across workflows.

Operational notices

Publish controlled content that support and incident workflows can reference safely.

Shared across Sendix sending

Build one content library for API sends, broadcasts, and automations.

Start free, create your first template, and move reusable content out of ad hoc code strings when it deserves preview and version control.

Create free accountCompare plans
FAQ

Template questions before production content moves into Sendix.

The main concerns are whether templates are optional, how variables are checked, and how versions reach production sends.

Can I still send raw HTML?

Yes. Templates are optional. They are most useful for reusable production content that benefits from preview data, version history, and a stable reference.

Can API sends reference a template?

Yes. API, broadcast, and automation surfaces can reference published template content instead of embedding the full HTML in every send path.

How do variables get checked?

Use preview or render paths with sample JSON. That lets the team inspect the rendered subject and HTML before publishing or sending.

Do template edits immediately change production email?

Use the published version as the production reference. Draft edits can be reviewed, duplicated, previewed, and published intentionally.

Ready to send your first email?

25,000 emails free every month. No credit card required. Upgrade only when you outgrow the free tier — and we will let you know when that time comes.

Create free accountTalk to sales

Managed SaaS platform · Native SMTP engine · SOC 2 in progress