Templates changelog

The drag-and-drop editor saves your work every few seconds. Those autosaves no longer close the editor in templates and campaigns.

Uploading images from the editor’s file manager works again, and uploaded images are served from Emailit’s CDN. See Template editors.

• Import a Dragit .json file, an .html file or a .zip package with images. Images are uploaded to Emailit’s CDN and their links are rewritten.
• Export a template as Dragit JSON, HTML or ZIP from its menu.
• Sort the templates list, and use the searchable template picker in campaigns and automations to reach every published template.
• Save as template on a campaign copies its subject, sender, reply-to address, content and editor into a new template.

See Import and export templates.

Temple supports variables with nested paths such as {{order.items.0.sku}}, default values such as {{first_name|"there"}}, and {{#if plan}}…{{else}}…{{/if}} blocks. Missing variables render as empty text.

The reference also explains where Temple runs: in API sends that use a template or variables, and in automation Send email steps. Campaigns use their own merge tags, and SMTP mail isn’t templated. See Temple.

Design a timer in the countdown builder and copy its image URL into your email or template. The image is generated each time it’s loaded, so it shows the time left until your deadline. Images can be 100 to 1,200 pixels wide.

Build templates with the HTML editor, the rich-text editor or the Dragit drag-and-drop editor. Templates that share an alias are versions of one template, and only the published version is used when you send by alias.

Manage templates with the Templates API, and send one by passing template and variables to Send an email. See Templates.