MailPoet Automations
How to Remove a Subscriber From a MailPoet List When a WooCommerce Order Is Refunded
If a refunded buyer stays on your customers-only list, they keep getting customer-only emails. Zapify can take them off automatically when the order is refunded, using the free An order changes status trigger and the Remove a subscriber from lists action. MailPoet is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: An order changes status (
WC_ORDER_STATUS_CHANGED, WooCommerce) with New status = Refunded - Action: Remove a subscriber from lists (
MAILPOET_REMOVE_SUBSCRIBER, MailPoet)
When an order moves to Refunded, Zapify unsubscribes the buyer — found by their billing email — from the lists you choose.
What
The subscriber is unsubscribed from that list only. They stay in MailPoet, and their other lists and tags are untouched. To unsubscribe someone from everything, use the unsubscribe action.
PRO feature
MailPoet is a Zapify PRO integration. The MailPoet action used in this automation needs an active Zapify PRO licence.
No Connection needed
MailPoet runs on your own site rather than somebody else's server. There is no API key to paste and nothing to set up under Settings → Connections — the integration only needs MailPoet installed and active.
Before you start
- WooCommerce and MailPoet installed and active.
- The list you added buyers to — see adding a WooCommerce customer to MailPoet.
How to build the automation
Step 1: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Remove refunded buyers from the customer list.
Step 2: Add the "An order changes status" trigger
- Click Add Trigger.
- Choose WooCommerce as the app.
- Select the trigger An order changes status.
Set New status to Refunded. Leave Previous status on Any.
Step 3: Add the "Remove a subscriber from lists" action
- Click Add Action.
- Choose MailPoet as the app.
- Select Remove a subscriber from lists.
Step 4: Configure the action
| Field | Required | What it does |
|---|---|---|
| Subscriber email | No | Insert the Billing email token so the right subscriber is found, including guest customers. |
| Lists | Yes | Pick one or more lists to take them off. |
Step 5: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.
Step 6: Test it
Refund a test order. Open the subscriber in MailPoet → Subscribers and check the list shows as unsubscribed, or open Zapify → Logs to confirm the run.
Tokens you can use
The An order changes status trigger exposes Order ID, Order number, Order status, Order total, Billing email, Billing first name, Billing last name and more. After the action runs it exposes Subscriber ID.
Conclusion
With the free An order changes status trigger and the Remove a subscriber from lists action, MailPoet stays in step with refunds. Pair it with a purchase automation that adds buyers to the list.
FAQs
Is this free in Zapify?
The trigger is free. Remove a subscriber from lists is part of the MailPoet PRO integration and needs an active Zapify PRO licence.
What if the buyer is not a subscriber?
Nothing is changed and the run is recorded as skipped with the reason, not as a failure. This action never creates anyone.
Does it delete the subscriber?
No. They are unsubscribed from the chosen lists and stay in MailPoet.
Can I do this on other statuses too?
Yes. Set New status to Cancelled or Failed, or build one automation per status.
Do I need to write any code?
No. Everything is configured visually.