Automations Changelog
Release notes for the Automations addon — the workflow builder that runs multi-step email journeys against your contacts.
The addon follows a major.minor versioning scheme and updates through the in-app Addons updater (Addons → Automations → Update). You can review what changed in any available update before installing it.
Version history is recorded from 3.1 onward, the release in which the addon gained its changelog.
Releases
| Version | Release Date | Type | Highlights |
|---|---|---|---|
| 3.2 | October 2026 | Reliability | Segment-sent broadcasts start open/click automations, paused automations resume cleanly, Copy/Move steps start the next automation, staff share automations, and a long list of fixes |
| 3.1 | August 2026 | Deliverability & Reliability | List-Unsubscribe header on the Send an Email action, plus fixes for open/click triggers and Triggers-tab settings |
Automations 3.2
Release Date: October 2026 Type: Reliability Release Previous Version: 3.1
Automations 3.2 closes the gaps customers hit most often when building a sequence: an automation now starts from a broadcast sent to a segment, pausing no longer strands contacts, the Copy and Move steps start the next automation, and staff accounts work on each other's automations the way they already share lists. It also closes an access-control gap and fixes a long list of smaller issues. The update installs through the Addons updater with no manual steps.
Two items depend on the core application: double opt-in contacts entering an automation when they confirm, and the core trigger actions Copy contact to another list and Move contact to another list starting the destination list's automations. They work once Mumara Campaigns 7.2 is installed.
Highlights
| Area | Summary |
|---|---|
| Segment sends | Open and click automations start for a broadcast sent to a segment built on the automation's list |
| Pause and resume | Contacts are parked where they are and carried on when the automation resumes |
| Copy and Move steps | Carry the contact's status and start the destination list's automations |
| Staff accounts | Open, edit and view statistics for every staff account's automations |
| Access control | Automations, templates and broadcast content answer only to the account that owns them |
Enhancements
- Automations start from segment-sent broadcasts. An automation with the trigger When a contact opens an email or When a contact clicks on a link now runs when the broadcast was scheduled to a segment, as long as the segment is built on a list the automation uses. Previously only a broadcast scheduled directly to the list could start it, and an Any List automation did not start for a segment send either. The automation's own broadcast filter and custom criteria still apply.
- Staff accounts share automations. A staff admin can open, edit and view statistics for automations created by another staff account. Opening one no longer returns a Not Found page, and Statistics → Automations lists them all. Client accounts still see only their own.
- Pausing parks contacts and resuming carries them on. While an automation is paused, each contact is parked at its current step and nothing is sent. On resume, steps that came due during the pause run at once and the rest continue on schedule. A step deleted while paused simply ends that contact's journey.
- Copy and Move steps keep status and start automations. A copied or moved contact carries its unsubscribed, bounced, complained, suppressed and confirmed status into the destination list, an overwrite keeps the destination's existing opt-outs, and the destination list's automations take the contact as they would one added by hand. A safeguard stops two automations passing a contact back and forth between their lists.
- Double opt-in contacts enter when they confirm. A contact still awaiting confirmation now enters the automation at the moment they confirm. The Skip Un-confirmed switch, which had no effect, is hidden. Needs Mumara Campaigns 7.2.
- Specific Date criteria honour every condition the form offers: starts with, ends with, less than, greater than, after, before, exactly, between, is due in and is overdue for. Previously only is, isn't, contains and doesn't contain filtered, and any other condition let every contact through.
- Accurate statistics columns. Audience names every list, Trigger Action shows the event that starts the automation, Total Actions counts the steps that ran, and Last Activity reflects the latest send.
- Select Workflow Email offers emails that track clicks as well as opens, flagged with what each tracks, and refuses a condition the chosen email cannot track.
- List page. A select-all checkbox with Tools → Delete Selected, each column sorts by what it shows, and an automation without lists reads Not set.
- Plan & Usage shows the limits actually enforced for the account instead of Unlimited, and the usage alert warns from 70% and turns red from 90%.
- Sending-node pickers offer active nodes only, and the Sending Node sender option is hidden when the node has no usable From address of your own.
- Open and click expiry is enforced whether or not open and click log retention is switched on.
Fixed
- The trigger popup and the Settings tab showed an empty Choose a Contact List field when the automation's lists had been created by another admin, and confirming it would have replaced the real selection.
- Automations, saved templates and broadcast content could be opened, changed, exported or deleted from another account.
- The suppression list was never consulted, and a contact who unsubscribed, complained or was suppressed during a wait step still received the remaining emails.
- Contacts whose email address had been verified never entered an automation.
- Resuming after an action-limit pause or a sending-node outage left contacts stuck.
- Two running automations on the same lists collided on open and click events, so only one of them tracked a contact.
- If time passed on same day reset to Send Now after editing a later step.
- Automations created from a template with an open, click or birthday trigger never fired until re-saved, and a template automation started with Any List, so it could be started before its trigger was set up.
- The automations list showed an error for an account whose action limit is zero or unset, and the per-column search failed.
- Automations Stats checked the permission against the account's own role instead of its package role.
- An automation on a blocked list did nothing silently; it now shows a warning and skips new entries while it keeps running.
- Several labels, toasts and dialogs showed raw keys or hard-coded English, the Excluded Year check used 30 days instead of 365, removing a step said the automation had been deleted, and the import dialog asked for a zip instead of a JSON file.
- Every tracked open was written to the application log, and the statistics page carried unused charts.
Automations 3.1
Release Date: August 2026 Type: Deliverability & Reliability Release Previous Version: 3.0
Automations 3.1 brings the Send an Email action in line with the unsubscribe options already available when scheduling a campaign, and fixes two issues that could stop an automation running as expected. The update installs through the Addons updater with no manual steps.
Highlights
| Area | Summary |
|---|---|
| List-Unsubscribe | The Send an Email action can add a List-Unsubscribe header, with separate options for the link and the email address |
| Open & click triggers | Automations now run reliably on the open and click events |
| Triggers settings | Automation settings now save on every queue configuration |
Enhancements
-
List-Unsubscribe header on the Send an Email action. Each Send an Email step can now add a List-Unsubscribe header to the messages it sends, with separate switches for including the unsubscribe link and the unsubscribe email address — the same options you already have when scheduling a campaign or configuring a drip group. The address is pre-filled from the one set under Settings → General, and supports the sending-domain placeholder so a single automation can present the right address across multiple sending domains.
Mailbox providers use this header to offer a one-click unsubscribe control next to your message, which reduces the chance of recipients reporting it as spam and is expected by the bulk-sender requirements at the major providers.
The option is off by default, including on automations created before this release, so nothing changes until you enable it. It is independent of the existing Unsubscribe-Link switch, which controls the unsubscribe link placed inside the email body.
Fixed
- Automations now run reliably on open and click events. Workflows triggered by when a contact opens an email or when a contact clicks on a link could discard the very first open or click, leaving the automation waiting for an event that had already happened.
- Automation settings now save on every queue configuration. On the Application Settings → Triggers tab, turning Automation Status on and saving silently discarded that block of settings — including the waiting-pool driver and the list-selection options — on any installation not running the database queue. Saving now works regardless of how background work is configured.
Breaking Changes
None. 3.1 is fully backward-compatible with 3.0 — no configuration changes and no manual steps. Existing automations keep their current behaviour, and the new List-Unsubscribe option stays off until you switch it on.
Last updated on August 5, 2026