Since Notifuse 20, you can build automations: email journeys that start on their own when a contact does something. A signup gets a welcome series, a purchase gets a follow-up a week later, a trial that starts gets its onboarding emails. You draw the journey once, on a canvas, and Notifuse runs it for every contact who sets it off.

Triggers

A journey starts with a trigger, which is an event on the contact's timeline. Five kinds of events can start one:

  • A contact is created, updated or deleted. An update trigger can be limited to the fields that matter, such as a plan stored in a custom field or, since Notifuse 43, the contact's tracking consent.

  • On the list you pick, a contact subscribes, confirms, unsubscribes, resubscribes, bounces, complains, is pending or is removed.

  • A contact joins or leaves a segment.

  • An email is opened, clicked, bounced, reported as spam or used to unsubscribe. Since Notifuse 44, Clicked a link starts a journey the first time a contact clicks each link of an email, and can be limited to links containing some text, to one broadcast or to one template.

  • Your application sends a custom event through the customEvents API, such as trial_started or purchase.

A trigger fires once per contact or every time the event happens.

Entry conditions

Since Notifuse 38, a trigger takes entry conditions, built with the same editor as your segments: a trigger on purchase with "country is Germany" enrolls German buyers only. Unlike a Filter after the trigger, a contact who doesn't match is never enrolled, so with Once per contact they keep their entry for later. A count of past activity includes the event that fired the trigger: "opened at least 3 emails" enrolls on the third open.

The list

Anyone whose event matches can enter: to keep a journey to your subscribers, add an entry condition on list subscription. An automation that sends email belongs to one of your lists, and its emails carry that list's unsubscribe link. Before each marketing or blog email, Notifuse checks the contact on that list: one who unsubscribed, bounced or reported spam leaves the journey instead of getting the email. Transactional templates still go out.

The nodes

  • Email sends one of your templates, with its Liquid variables filled from the contact, in their language when the template has a translation. Since Notifuse 44, the email can use the event that started the journey as {{ trigger_event }}: a custom event's properties ({{ trigger_event.properties.items }}), the list or segment the contact joined, or the link clicked. Since Notifuse 27, each Email node can use another email integration than the workspace default, to warm up a new IP or spread the volume.

  • Delay waits from 1 to 365 minutes, hours or days.

  • Filter splits the journey in two, Yes and No, with your segments' conditions: contact fields, list subscriptions, opens and clicks, goals. A click can be narrowed to a broadcast or to a link whose URL contains /pricing (Notifuse 36), and a goal can be negated: "has not purchased in the last 30 days" (Notifuse 37).

  • A/B test splits contacts between two to four paths by weight. The same contact always takes the same path.

  • List status takes one of three paths for a list you pick: not on the list, active, or any other status.

  • Add to list and Remove from list change the contact's subscriptions. Adding can subscribe directly or leave them pending.

  • Webhook posts the contact to your URL, with an optional bearer secret. Since Notifuse 42 it refuses private addresses unless you set WEBHOOK_DELIVERY_ALLOW_PRIVATE_HOSTS=true, to reach n8n on your own network.

Every node takes an optional description, shown under its title on the canvas. A node whose output isn't linked to anything ends the journey there.

Exit on reply

Since Notifuse 33, an automation can stop for a contact the moment they reply to one of its emails, so a prospect who answers doesn't get the follow-ups. It works with Mailgun and Amazon SES; its own post explains the setup. Since Notifuse 44, a reply whose subject is only "stop", "unsubscribe", "remove", "remove me" or "opt out" ends the journey like any other reply, and changes no list subscription.

Three journeys

Welcome series

Trigger: List → Subscribed on your newsletter, once per contact. An email right away, a 2-day delay, a second email, a 5-day delay and a third one. Put a Filter before the third: contacts who clicked a link containing /pricing get answers to pricing questions, the others a customer story.

Trial onboarding

Trigger: the trial_started custom event. Day 1, a getting-started email from the founder, with Exit on reply on, so a user who answers gets a person instead of the next automated email. Day 3, a Filter on a custom field your app updates, such as the number of projects: tips for the next step, or a nudge to create the first project. Day 12, a Webhook tells your sales tool which trials are still active.

Win-back

Trigger: the purchase event your shop sends as a Purchase goal, every time. A 45-day delay, then a Filter: has not purchased in the last 30 days. A customer who bought again since takes the No path, which ends there; the others get a reason to come back.

Draft, live, paused

An automation starts as a draft, with nobody enrolled. Activate it and contacts enter as their events happen. Pause it to stop new entries: contacts already inside wait at their current step and carry on when you activate it again. You edit a draft or a paused automation, and a live one opens read only; a contact waiting on a step you delete leaves the journey.

Stats

Each automation counts the contacts who enrolled, completed, exited or failed. A contact exits when they reply with Exit on reply on, when a marketing email finds them unsubscribed, or when their step is deleted. Since Notifuse 44, the Stats switch on the canvas shows each step's results over the last 7 or 30 days or all time: the journeys that reached it and those waiting or retrying there, each split's share on its link, and for an email the messages sent, delivered, opened and clicked. The automations.nodeStats API gives the same figures. A contact's timeline shows each automation they entered and left, with the reason, and the automations.nodeExecutions API gives their journey step by step.

How it runs

When you activate an automation, Notifuse turns its trigger into a PostgreSQL trigger on the contact timeline: entry conditions are checked and the contact enrolled in the same transaction that writes the event, so a burst of signups doesn't wait on a queue.

A scheduler then moves contacts along every ten seconds by default, in batches shared fairly between workspaces. A contact moves through consecutive steps until it reaches a delay, with no limit on how many since Notifuse 43, and its position is saved after every node, so a restart picks up at the next step. Emails share the broadcasts' queue and the rate limit set on their email integration. A failing node, such as a webhook that doesn't answer, is retried after 2 then 4 minutes before the journey fails.

Not yet

  • The console's timeline shows entries and exits, but a journey's node-by-node history is only in the API.

  • An email can start a journey when it is opened or clicked, but not when it is sent or delivered.

  • Filter splits in two, and List status in three on one list, so routing on several values of a field takes several filters in a row.

  • You can't edit a live automation. Pause it, change it, then activate it again.

Getting started

Open Automations and create one: name it, pick its list if it sends email, set the trigger and its entry conditions, add your nodes and activate it. The automations documentation describes each trigger and node, and the custom events documentation shows how to send your application's events and goals.