Since Notifuse 28, an email template can carry a translation for each language of your workspace. A broadcast, an automation or a transactional email then reaches each contact in their own language. Your French subscribers get the French version, your Spanish customers get the Spanish one, and everyone else gets the original. You keep one template and send one broadcast or one API call, with nothing to branch on.
Workspace languages
Languages are set in Settings → General. Supported languages, in the Language & timezone panel, lists the languages your workspace writes in. You choose them among 31, from Arabic to Vietnamese, and Brazilian Portuguese and Traditional Chinese have their own entries. Default language is the one your templates are written in first, and the version a contact gets when nothing better matches. If the workspace has a single language, the template editor shows no translation controls at all.
Writing translations
Once the workspace has more than one language, the template editor has three tabs: Settings, Content in the default language, and Translations, with a switch for each other language. When you switch a language on, Notifuse copies the original subject, preview text and content into it as a starting point. Then you translate:
Subject and Subject preview, the line inboxes show after the subject. Both are required for each language you switch on, and the card shows them on a phone as you type.
The content, in a full-screen editor. That is the visual builder or the MJML code editor, whichever the template was created with: you choose between the two when you create a template, and its translations follow. A translation's visual editor can also import an MJML or JSON file into its language, and export that language's email.
The text version, for mail clients that show text only. Each language gets one generated from its own content at every send, unless you write your own in the editor's Text version mode.
After a big change to the original, Reset copies it over a translation again. If you switch a language off, its translation is removed when you save the template.
Liquid included
A translation is a whole email, with the same Liquid variables as the original. Take a welcome email whose English subject is Welcome, {{ contact.first_name }}. The French translation says Bienvenue, {{ contact.first_name }}, the Spanish one Te damos la bienvenida, {{ contact.first_name }}, in the subject as in the body. A translation can also change more than the words, with another picture for the Spanish market, a link to your French help center or a shorter layout.
Which version
At send time, Notifuse reads the contact's language field:
Empty, or the workspace's default language: the original.
A language the template has a translation for: that translation, with its own subject, preview text and content.
Any other language: the original.
Since Notifuse 44, a translation leaves from the sender chosen on the template, with its Reply-To, as the original does.
Since the original is always the fallback, a missing translation never means an empty email, and you can translate your most-read templates first and the rest later.
Every send
The same rule applies wherever a template goes out: in broadcasts, in the Email nodes of automations, in transactional emails sent through the API, and in the double opt-in confirmation of a list. A newsletter for English, French and Spanish readers is one broadcast, with its stats in one place. Its web version, behind {{ view_in_browser_url }}, shows each contact the language they were sent.
Contact language
A contact's language is one of their standard fields, and you can set it in several ways:
Through the API, in the
languagefield ofcontacts.upsert, or in a Language column of a CSV import.By hand, on the contact in the console.
In the notification center, the preferences page your emails link to. It speaks 11 languages, and a contact who picks one there saves it as their language. A contact with no language yet gets their browser's language, saved at their first click or key press on the page and never on load, so security scanners that open links in emails don't change it.
In a transactional API call, as below.
Language is also a field in segments, so you can count your Spanish speakers or send them a broadcast of their own.
Through the API
Say your order_confirmation transactional notification uses a template written in English with a Spanish translation, whose subject is Tu pedido {{ order.number }} está confirmado. Send it with the contact's language, in a POST to /api/transactional.send:
{
"workspace_id": "acme",
"notification": {
"id": "order_confirmation",
"channels": ["email"],
"contact": {
"email": "lucia@example.com",
"first_name": "Lucía",
"language": "es"
},
"data": {
"order": { "number": "1042", "total": "49,90 €" }
}
}
}Lucía gets the Spanish email, filled with her order. If the API key can write contacts, the language in the call is saved on the contact before the send. Otherwise Notifuse uses the language already stored. Leave out email_options.subject and email_options.subject_preview to keep the translated ones, because an override is one text for every language.
Preview and test
Once a template has a translation, its Preview and its Send test email dialog both get a Language selector, so you can check the Spanish version before your Spanish customers see it.
Licence
Since Notifuse 40, on a self-hosted installation, adding a language to a template or editing a translation needs a licence key, Studio or above. Translations already saved are still sent whatever the licence state, and you can always switch one off. The same page says which Notifuse Cloud plans include translations.
The console
The console itself is available in eight languages: English, French, Spanish, German, Catalan, Brazilian Portuguese, Japanese and Italian. Since Notifuse 32, each user's choice is saved on their account and follows them from one browser to another. Notifuse's own emails use it too. Your sign-in code arrives in your language, an alert about a paused broadcast in each owner's, and a workspace invitation in the language of the member who sent it.
Not yet
There is no regional fallback. A contact's language must match a translation's code exactly:
fr-CAdoesn't get thefrtranslation, andptdoesn't getpt-BR. The notification center saves a browser's language as two letters, so a Brazilian browser givespt.You can't switch editors. A template and its translations stay in the mode they were created in. To move from visual to MJML code, or back, create a new template and bring the content over with Export MJML and Import MJML.
Getting started
Add your languages in Settings → General, open a template and switch a language on in its Translations tab, then set your contacts' language. The templates documentation describes translations and Liquid, the contacts documentation the language field, the notification center documentation its languages, and the transactional API documentation the send call.
