Notifuse 44 is the biggest release in the history of Notifuse. Its changelog has 194 entries. The largest release before it, Notifuse 15, had 54.

Almost every screen of the console was rebuilt on a new design system. Every email now has a plain-text version and can link to its web version. The email editor moves to MJML 5. And the two engines behind every email, safe-mjml and liquidgo, are now open-source projects of their own.

New console

The console has a new, denser look: the Inter typeface, new colors and tighter spacing. A lighter sidebar replaces the top bar. It folds to icons and stays open once you pin it.

The contacts page of Notifuse 44, with lists and segments in a side rail
  • The dashboard shows website visits, how your rates moved since the previous period, emails sent each day by origin, the latest failures and your upcoming broadcasts.

  • Contacts, lists and segments share one page. A contact opens in a sheet with its own link, and J and K move through the table.

  • The automation editor is a full-screen canvas. Its Stats switch shows each step's results.

  • Each transactional notification shows its open and click rates, its last send and the API call in cURL, TypeScript and Python.

  • Settings, templates, logs, the file manager and the blog page all have new layouts.

Email editor

The visual editor now writes MJML 5. Sections get a column gap, and Text blocks can hold real headings, H1 to H6, which screen readers use to jump between sections.

A Library tab beside Structure shows your saved blocks with previews. A block can also carry a display condition, such as order.total is greater than 100, so it only goes to some recipients.

New templates start from a gallery of 15 ready-made emails: a verification code, a receipt, an order confirmation, an abandoned cart, a newsletter and others, written in your workspace's language.

Plain text

Every email now includes a plain-text version, for mail clients that show text only and for better deliverability. Notifuse generates it from the HTML at every send.

You can also write your own in the Text version mode of the template editor, with Liquid, as in the subject.

Web versions

Broadcast and automation emails can link to their web version with {{ view_in_browser_url }}. The page shows the email as it was sent, in its language and with the data of that send.

Viewing it records no open, and its links record no click.

Automations

The new Clicked a link trigger starts an automation the first time a contact clicks a link in an email. You can limit it to some links, to one broadcast or to one template.

The automation editor with its Stats switch on, showing each step's results

Automation emails can also read the event that started the journey, as {{ trigger_event }}: a custom event's properties, the list or segment the contact joined, or the link clicked.

Broadcasts

A scheduled broadcast can go back to draft before it starts sending. Each variation, in an A/B test too, can send from its own sender. And an A/B test can be paused or cancelled during its test.

A broadcast detail page: funnel, opens and clicks per hour, A/B test results and clicked links

safe-mjml

Every email Notifuse sends is compiled by safe-mjml 1.1, our open-source MJML compiler for Go. It writes the same HTML as the official MJML 5.4.1, and it keeps Liquid tags intact.

It was built to compile templates written by people you don't fully trust, without running JavaScript. The safe-mjml post explains how we built it.

liquidgo

Liquid is rendered by liquidgo 5.14.6, our Go port of Shopify Liquid. Templates now behave as they do in Shopify Liquid in many more cases.

liquidgo also puts a budget on every render, so a template that would loop forever is stopped in a fraction of a second. The liquidgo post explains how.

Self-hosting

The compose.yaml file now installs Notifuse from the published image and moves to PostgreSQL 18. An installation on PostgreSQL 17 is upgraded by its next docker compose up -d, after a copy of its data. Notifuse still runs on PostgreSQL 17.

The workspace list now tells root users and workspace owners when a new version is out. CHECK_FOR_UPDATES=false turns it off.

Before upgrading

If you run your own instance, check these points first:

  • Notifuse now needs PostgreSQL 17 or later.

  • Liquid outputs are HTML-escaped in emails. Data meant to be HTML needs the new raw filter: {{ global_feed.html | raw }}.

  • An email whose Liquid fails is no longer sent. The preview and the test send show the error.

  • If you set email.text through the API, it is now sent as the email's text version.

  • The first start builds new indexes, and sending waits meanwhile. Upgrade outside a large send.

Every point is in the Before you upgrade section of the changelog.