Reference
Templates changelog
Changes to Templates: new features, improvements and fixes.
October 2026
Fixed
API accepts single reply-to addresses, Unix keep_until and one run ID
REST APITemplatesSuppressionsAutomations
- Create and update a template accept
reply_toas one address or a one-item list. Before, both returned 400 “must match exactly one schema in oneOf”. - Create and update a suppression accept
keep_untilas a Unix timestamp, andnullclears it on update. - Automation stats accepts a single
run_ids[]value.
- Create and update a template accept
Changed
Campaigns render with Temple
- Temple in every campaign: campaigns built with the HTML, rich-text and Dragit editors, or through the API, now render with Temple for each recipient. A template that uses fallbacks or conditionals renders the same in a campaign as in a contact automation. Before, campaigns replaced only the five merge tags and sent
{{first_name|"there"}}and{{#if}}blocks as typed. - Existing merge tags keep working:
{{first_name}},{{last_name}},{{email}},{{unsubscribe_url}}and{{cf.<key>}}render as before, in any letter case. Spaces inside the braces are now allowed, so{{ unsubscribe_url }}becomes a working link. - Custom fields as
{{custom_fields.<key>}}: campaigns accept the form automations use, as well as{{cf.<key>}}. - Unknown placeholders render as empty: any other
{{…}}text in a campaign is now removed instead of being sent as typed. Check older campaigns with Preview as contact before you send them.
See Merge tags and Temple.
- Temple in every campaign: campaigns built with the HTML, rich-text and Dragit editors, or through the API, now render with Temple for each recipient. A template that uses fallbacks or conditionals renders the same in a campaign as in a contact automation. Before, campaigns replaced only the five merge tags and sent
New
MJML editors in alpha
Templates and campaigns can now be written in MJML, the markup language for responsive email. MJML is in alpha: it’s open only to the Emailit team while we test it, and customer workspaces don’t see it yet.
- Two editors: the MJML Visual Editor (drag and drop on the rendered email) and the MJML Code Editor (autocomplete, inline validation and a live preview). Both are versioned and start at 0.2.0.
- Temple in any content or attribute, with conditional blocks around components and a preview with sample data. MJML campaigns render Temple for each recipient.
- Editing together: teammates who open the same template or campaign edit one shared draft in real time, with presence, cursors and per-person undo.
- MJML API: Validate MJML, Render MJML and Retrieve the MJML reference, plus
editor: "mjml"on templates. On the MCP server, the Emailit team gets the matching tools.
Until MJML leaves the alpha, other requests that create or change MJML return
403witherror: "mjml_alpha". Existing MJML templates and campaigns send for everyone, and a campaign’scontent_type: "mjml"stays the plain label it was. See MJML editors and API.Fixed
Nested Temple conditionals and {{cf.*}} in automations
- Nested conditionals: Temple now resolves the innermost
{{#if}}blocks first, so every{{else}}and{{/if}}belongs to its own block. Nesting works up to 10 levels deep. Before, an inner block closed the outer one early. {{cf.<key>}}in automations: contact automations fill custom fields as{{cf.<key>}}as well as{{custom_fields.<key>}}, so a template written for campaigns works in automations too.
See Temple and Automation emails.
- Nested conditionals: Temple now resolves the innermost
September 2026
Fixed
Dragit editor fixes
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.
New
Template import, export and picker
- Import a Dragit
.jsonfile, an.htmlfile or a.zippackage 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.
- Import a Dragit
Improved
Temple templating reference
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
templateorvariables, and in automation Send email steps. Campaigns use their own merge tags, and SMTP mail isn’t templated. See Temple.
July 2026
New
Countdown timer images
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.
February 2026
New
Templates and the Templates API
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
templateandvariablesto Send an email. See Templates.