When a TimeRex event is cancelled, remove the attendee from a MailPoet list

When a TimeRex booking is cancelled, this workflow removes that attendee from the MailPoet list or lists you choose, so people who no longer plan to attend stop getting the emails meant for those who do.

TimeRex

MailPoet

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.8k sites Free to import

The When a TimeRex event is cancelled, remove the attendee from a MailPoet list workflow on the FlowMattic canvas, with 2 steps across TimeRex, MailPoet — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Many hosts keep a MailPoet list for each event, webinar or session type and use it for reminders and prep material. When someone cancels in TimeRex, they stay on that list unless you remember to take them off. This workflow removes them for you.

The TimeRex trigger, Event Cancelled, runs as soon as TimeRex reports a cancelled booking. The booking details, including the guest's email address, are passed to FlowMattic.

The MailPoet step removes an existing subscriber from one or more lists. Map the attendee's email so MailPoet can find them, and pick the lists to take them off. They stay a MailPoet subscriber and remain on any other lists. The step only works on people who are already subscribers, so this suits sites where bookers are added to MailPoet when they schedule. For anyone MailPoet does not know, nothing changes, and the run's entry in Task History shows MailPoet's response.

Webinar reminder list

Registrants who cancel in TimeRex come off the webinar's MailPoet list, so the reminder emails and the replay link go only to people still attending.

Workshop prep emails

A trainer sends homework before each workshop. Removing cancelled attendees from the workshop list keeps those emails to the people who will show up.

Consultation follow-up sequence

A list feeds emails before a consultation. When the booking is cancelled, the person leaves that list and stops receiving them.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
TimeRex Event Cancelled
Starts a run for each cancelled TimeRex booking. The guest's details, including their email address, are passed on to MailPoet.
Step 2Action
MailPoet Remove Subscriber From List(s)
Removes the attendee from the MailPoet list or lists you choose. Map the attendee's email so MailPoet can find the subscriber, then pick the lists.

What you need

FlowMatticCore
TimeRex AccountAccount
MailPoet PluginPlugin

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Pair this with a TimeRex Event Confirmed workflow that uses MailPoet's Create New Subscriber and Add Subscriber to List(s) actions, so cancelling guests are already on the list to remove.
Test after import with an email that is already on the list, then check in MailPoet that the subscriber has left only the lists you picked.
If you also want a record of cancellations, add a Google Sheets step after MailPoet that logs the guest's name, email and booking details.