Templates

Template lifecycle

• Visual and source editing
• Variable preview with realistic data
• Version history and publish state
• Shared templates across customer Runtimes
• Transactional and lifecycle starter templates

await send.emails.send({
  from: "hello@example.com",
  to: "customer@example.net",
  template: "welcome",
  variables: { name: "Mina" },
});

Publish a new version instead of changing content used by an in-progress workflow.

Create and preview

Open Templates, create a stable ID and edit subject plus text/HTML in the visual editor. Define realistic preview variables and test dark/light, mobile width, missing values and links. Use Preview before Test send; a preview validates rendering, while a test also validates domain, Runtime and delivery path.

Environments and versions

Keep drafts in development, promote reviewed content through staging and production, and select the environment explicitly from SDK/API calls. Publishing creates a version; Automations pin the version accepted by each run. Use version history and rollback rather than editing evidence away.

Quality and delivery-impact checks identify missing text, unsafe links and content risks but cannot guarantee inbox placement. Deleting a template referenced by active workflows or campaigns should be avoided; publish a replacement and migrate callers first.