How do I specify the locale in an event?

Add a top-level locale field to your event payload (e.g. "locale": "de"). else.events uses this to route to the correct template variant.

What happens if a template does not exist for the requested locale?

else.events falls back to the workspace default locale (typically "en"). You can configure the fallback locale per workspace.

Can I manage translations without a developer?

Yes. Template locale variants are managed in the else.events UI. A product manager or translator can update copy without a deployment.

Is there a limit on the number of supported locales?

No hard limit. You can add as many locale variants to a template as needed.

Transactional emails in the user's language — without template duplication

Include a locale in your event payload. else.events routes to the right language template automatically. One API call, any number of locales.

Build localised email workflows See template management

Why email localisation is harder than it should be

Duplicate templates per language clutter the codebase

welcome_en.html, welcome_de.html, welcome_fr.html — for every template, every locale, every update.

Locale detection logic ends up in your application

Your backend has to determine the user's locale, select the right template file and pass both to the email provider.

Translation updates require deployments

A typo fix in the French welcome email still needs a commit and a deploy if templates live in your repo.

Fallback handling is manual

When a locale is not yet translated, the fallback to English is custom logic you have to write and test.

One event, one API call — locale routing handled by rules

Pass locale in the event payload

Add a locale field to your event. else.events rules match on it and select the correct language template automatically.

Fallback locale configured per workspace

If a locale is not yet available for a template, else.events falls back to the configured default — no custom code needed.

Manage translations in the UI

Each template can have multiple locale variants. Edit or add a translation without touching your application.

No per-locale code branches

Your application fires a single event. Locale routing is a configuration concern, not a code concern.

// locale field drives template selection

Locale-aware event — same API call for every language

{
  "type": "user.signed_up",
  "locale": "de",
  "user": { "email": "nutzer@example.com", "name": "Alex" },
  "data": {
    "app_name": "MyApp",
    "getting_started_url": "https://app.example.com/start"
  }
}

else.events matches locale = de, selects the German welcome template and delivers it. Falls back to the default locale if a German variant does not yet exist.

Frequently asked questions

How do I specify the locale in an event?: Add a top-level locale field to your event payload (e.g. "locale": "de"). else.events uses this to route to the correct template variant.
What happens if a template does not exist for the requested locale?: else.events falls back to the workspace default locale (typically "en"). You can configure the fallback locale per workspace.
Can I manage translations without a developer?: Yes. Template locale variants are managed in the else.events UI. A product manager or translator can update copy without a deployment.
Is there a limit on the number of supported locales?: No hard limit. You can add as many locale variants to a template as needed.

Localised transactional emails — without template clutter

One event, one API call. else.events handles locale routing and fallback automatically.

Free during public beta
Fallback locale configured per workspace
Translations managed in UI