MailPoet Automations
How to Swap MailPoet Tags When a WooCommerce Product Is Purchased
Somebody who just bought should stop receiving "buy now" emails. Zapify can move a subscriber from your lead tag to your customer tag when a WooCommerce order is paid, using the free A product is purchased trigger with the Add a tag to a subscriber and Remove a tag from a subscriber actions. MailPoet is a Zapify PRO integration.
What this automation does
The automation is one trigger plus two actions:
- Trigger: A product is purchased (
WC_PRODUCT_PURCHASED, WooCommerce) - Action 1: Add a tag to a subscriber (
MAILPOET_ADD_TAG, MailPoet) - Action 2: Remove a tag from a subscriber (
MAILPOET_REMOVE_TAG, MailPoet)
When an order reaches a paid status, Zapify adds customer to the buyer's MailPoet subscriber and removes lead. Segment your MailPoet campaigns by tag and the lead emails stop on their own.
The buyer must already be a MailPoet subscriber
These actions change tags on an existing subscriber and never create one. If the buyer is not in MailPoet, adding the tag fails and removing it is skipped. To add buyers first, see adding a WooCommerce customer to MailPoet.
Removing needs a tag that exists
Unlike adding, a tag name that matches no tag in MailPoet is an error: The tag does not exist. That is nearly always a typo, so it is reported rather than ignored. Removing a tag the subscriber simply does not have is harmless.
PRO feature
MailPoet is a Zapify PRO integration. The MailPoet actions used in this automation need 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.
- Buyers who are MailPoet subscribers, using their billing email.
- Two tags: the one to add (
customer) and the one to remove (lead). The one to remove must already exist.
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 Move buyers from lead to customer.
Step 2: Add the "A product is purchased" trigger
- Click Add Trigger.
- Choose WooCommerce as the app.
- Select the trigger A product is purchased.
Set the Product field to the product that should start the automation, or leave it on Any.
Step 3: Add the "Add a tag to a subscriber" action
- Click Add Action.
- Choose MailPoet as the app.
- Select Add a tag to a subscriber.
Step 4: Configure the first action
| Field | Required | What it does |
|---|---|---|
| Tag names | One of the two | Type customer. It is created if it does not exist. |
| Subscriber email | No | Insert the Billing email token. |
Step 5: Add the "Remove a tag from a subscriber" action
- Click Add Action again, below the first one.
- Choose MailPoet as the app and select Remove a tag from a subscriber.
Configure it:
| Field | Required | What it does |
|---|---|---|
| Tag | One of the two | Pick the existing tag to take off. |
| Tag names | One of the two | Or type its name, such as lead. Matching is by name, so spell it exactly as in MailPoet. |
| Subscriber email | No | Insert the Billing email token again. |
Step 6: 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 7: Test it
Place a test order as a subscriber who has the lead tag and mark it as paid. Check MailPoet → Subscribers, or open Zapify → Logs to confirm both actions ran.
Tokens you can use
The A product is purchased trigger exposes Billing email, Billing first name, Billing last name, Product names, Order ID, Order total and more. Both actions expose Subscriber ID afterwards.
Conclusion
With the free A product is purchased trigger and the two tag actions, MailPoet always knows who has bought. To also take buyers off a list when an order is refunded, see removing a subscriber from a list on refund.
FAQs
Is this free in Zapify?
The trigger is free. The MailPoet actions are part of the MailPoet PRO integration and need an active Zapify PRO licence.
Why did removing the tag fail with "The tag does not exist"?
No tag in MailPoet has that name. Check the spelling, or pick the tag from the Tag list instead of typing it.
Does order matter?
Not for the result, but adding first means that if something goes wrong the buyer at least keeps one of the two tags.
Can I use this for other swaps?
Yes. Any "from this tag to that tag" move works the same way, with any trigger.
Do I need to write any code?
No. Everything is configured visually.