Skip to content

Omnisend integration

Omnisend HTML email templates, checked before they land

Build the email in code or on a canvas, run QA against Omnisend’s rules, and push an Omnisend email template imported from your HTML for every language in one step.

Start Building Free

What lands in Omnisend

Publish creates an Omnisend email template imported from your HTML for each language you select. You find it in Templates in Omnisend. Names follow a pattern such as {Template}_{LOCALE}, so October_update becomes October_update_EN and October_update_DE. You can rename each one in the dialog.

Pushing again replaces the template with the same name with the new version. Connecting takes an Omnisend API key. Sending, lists and scheduling stay in Omnisend.

Checked against Omnisend before the push

Once Omnisend is your active ESP, the email template checker reads every language with Omnisend’s syntax in mind. A missing unsubscribe tag is a blocker, not a footnote.

Unsubscribe tag
Looks for [[unsubscribe_link]] or [[unsubscribe]]. Missing means a blocker. Present but hidden or tiny is flagged as high risk.
Merge tags
Omnisend tags such as [[contact.first_name]] are left alone. A tag written for a different ESP is flagged, because Omnisend would print it as text.
Dead links
Every link is requested. A 404, 410, server error or timeout is a blocker.
Leftover tokens
A {{locale.*}} or {{theme.*}} token that did not resolve is a blocker. It would reach Omnisend as raw text.
Auto QA beside the German preview: two dead links and a missing Klaviyo unsubscribe tag listed as blockers, signals collapsed below.Auto QA beside the German preview: two dead links and a missing Klaviyo unsubscribe tag listed as blockers, signals collapsed below.

One HTML file, one Omnisend template per language

The layout lives in one Shared HTML file. Copy, links, images and the subject change per language through {{locale.key}} tokens, edited in a grid or imported from Excel. That workflow has its own page: HTML email localization.

Compile turns each language into plain HTML. Publish then sends each one to Omnisend as its own template. Fixing a link in the shared file fixes it in every language on the next push.

Imported as HTML, replaced on the next push

The push uses Omnisend’s HTML import, so the template is your compiled HTML. When you push again under the same name, the old template is removed and the new one is imported in its place. You do not end up with a list of near-identical copies.

Omnisend tags such as [[contact.first_name]] and [[unsubscribe_link]] pass through Compile untouched.

Questions

What happens to the old template when I push again?

It is replaced. The template with the same name is deleted and the new HTML is imported under that name.

Does EmailStitch send through Omnisend?

No. It pushes the template. Contacts, campaigns and automations stay in Omnisend.

What if I am not on Omnisend yet?

Download ZIP gives you the compiled HTML for every language, with nothing EmailStitch-specific inside. Push to any of the six supported ESPs later.

Push your next Omnisend template from one file

Create an account. Shared HTML, translations, QA, and ESP push in one workspace.

Start Building Free