Templates

Overview

Email templates in Notifuse are built using a visual drag-and-drop editor that combines:

MJML Framework: Guarantees full email client compatibility across all devices and email providers
Liquid Templating: Dynamic content personalization using variables like {{ contact.first_name }}
Version Control: Every template update creates a new version to track previously sent contents
Multi-Purpose: Used by both broadcast campaigns and transactional notifications

Template Builder Features

Drag-and-Drop Interface: Visual editor for easy template creation
Responsive Design: Mobile-optimized layouts that work across all devices
Pre-built Blocks: Headers, footers, buttons, images, and content sections
Brand Consistency: Colors, fonts, logos, and styling options
Real-time Preview: See exactly how your email will look before sending

Usage

Templates are used across Notifuse for:

Broadcast Campaigns: Mass email campaigns sent to your contact lists
Transactional Notifications: Automated emails triggered by user actions
Double Opt-In Emails: Sent when anonymous contacts subscribe to lists
Welcome Emails: Sent when contacts confirm their subsription to lists
Unsubscribe Confirmations: Sent when contacts opt out

Translations

A template can carry one version of its content per language. Which version a contact receives is decided at send time from the contact’s language field, so one broadcast or one transactional notification serves every language you have written — nothing to branch on in your automations or your API calls.

Enabling languages in the workspace

Translations are only offered for languages the workspace has switched on. Open Settings → General:

Supported Languages — the languages this workspace works in. Add every language you intend to write templates for; a language that is not listed here cannot be given a translation.
Default Language — the language a template’s main content is written in, and the version a contact receives when nothing better matches. Every workspace has exactly one.

Language codes are two-letter ISO codes such as en, fr, de, es. The default language must be one of the supported languages, and the list must contain at least one.

With a single supported language the template editor shows no translation controls at all. The Translations tab appears as soon as the workspace supports more than one language.

Writing a translation

When creating or editing a template, the editor has a tab per stage: Template, in the workspace’s default language, and Translations, listing each other supported language. Open a language to write its version: its own subject, preview text and body, with the same visual editor, MJML code mode and Liquid variables as the default. Reset translation copies the default-language content into the translation as a starting point, replacing whatever was there. A language that has no translation is simply skipped at send time — you do not have to translate a template into every supported language at once.

Which version a contact receives

At send time Notifuse reads the contact’s language:

If it is empty, or equals the workspace’s default language, the contact receives the default content.
If the template has a translation for that language, the contact receives that translation.
Otherwise the contact receives the default content.

So the default content is always the fallback, and a translation is only ever an improvement over it, never a gap. Set a contact’s language on import, through the API (language on contacts.upsert), or from a subscription form; see Contacts. To check a specific language before sending, the template preview and the test-send dialog both have a Language selector.

Self-hosted: adding a language to a template, or editing the content of an existing translation, needs a licence key. Translations already saved keep being sent in every licence state, editing the rest of a template that carries them is never refused, and removing a translation is always allowed. Every Notifuse Cloud plan includes it.

Liquid Syntax

Notifuse uses Liquid templating to insert dynamic content into your emails. Variables are enclosed in double curly braces and automatically replaced with actual data when emails are sent.

Contact Variables

The contact object contains the full contact profile with all stored information. Access any contact field for personalization:

Hello {{ contact.first_name }}!

Your account email: {{ contact.email }}
Full name: {{ contact.first_name }} {{ contact.last_name }}

Output Example:

Hello John!

Your account email: john.doe@example.com
Full name: John Doe

List Variables

Reference the mailing list information:

You're subscribed to: {{ list.name }}
List ID: {{ list.id }}

Output Example:

You're subscribed to: Newsletter
List ID: newsletter

System URLs

Use pre-generated URLs for common actions:

Unsubscribe Link

<a href="{{ unsubscribe_url }}">Unsubscribe from this list</a>

Subscription Confirmation

<a href="{{ confirm_subscription_url }}">Confirm your subscription</a>

Notification Center

<a href="{{ notification_center_url }}">Manage your preferences</a>

Complete Example

Welcome {{ contact.first_name }}!

Thank you for subscribing to {{ list.name }}. We're excited to have you on board!

Your registered email: {{ contact.email }}

Manage Preferences: {{ notification_center_url }}

Don't want to receive these emails?
Unsubscribe here: {{ unsubscribe_url }}

Available Data Structure

When designing templates, you have access to this data structure:

{
  "contact": {
    "first_name": "John",
    "last_name": "Doe",
    "email": "john.doe@example.com"
  },
  "list": {
    "id": "newsletter",
    "name": "Newsletter"
  },
  "unsubscribe_url": "https://your_notifuse_endpoint.your_website.com/notification-center?action=unsubscribe&email=john.doe@example.com&lid=newsletter&lname=Newsletter&wid=workspace123&mid=msg_123&email_hmac=abc123",
  "confirm_subscription_url": "https://your_notifuse_endpoint.your_website.com/notification-center?action=confirm&email=john.doe@example.com&lid=newsletter&lname=Newsletter&wid=workspace123&mid=msg_123&email_hmac=abc123",
  "notification_center_url": "https://your_notifuse_endpoint.your_website.com/notification-center?email=john.doe@example.com&email_hmac=abc123&wid=workspace123"
}

Getting Started

Features

Tutorials

Integrations

Email Providers

Overview

Template Builder Features

Usage

Translations

Enabling languages in the workspace

Writing a translation

Which version a contact receives

Liquid Syntax

Contact Variables

List Variables

System URLs

Unsubscribe Link

Subscription Confirmation

Notification Center

Complete Example

Available Data Structure

​Overview

​Template Builder Features

​Usage

​Translations

​Enabling languages in the workspace

​Writing a translation

​Which version a contact receives

​Liquid Syntax

​Contact Variables

​List Variables

​System URLs

​Unsubscribe Link

​Subscription Confirmation

​Notification Center

​Complete Example

​Available Data Structure

Overview

Template Builder Features

Usage

Translations

Enabling languages in the workspace

Writing a translation

Which version a contact receives

Liquid Syntax

Contact Variables

List Variables

System URLs

Unsubscribe Link

Subscription Confirmation

Notification Center

Complete Example

Available Data Structure