WooCommerce Wishlist: The Free Way To Automate Follow-Up Emails

What happens after a customer adds a product to their WooCommerce wishlist?

Usually, nothing…

They save the product because they like it but aren’t ready to buy yet. Maybe they’re comparing options, waiting for payday, or simply want to come back later.

But once they leave your store, that wishlist item is just sitting there waiting for them to return.

A customer already told you what they want. Why wait for them to come back on their own?

You could keep sending your regular promotional emails and hope they notice that product again. You could spend more on ads to bring them back. Or you could follow up with them based on the exact action they already took: adding something to their wishlist.

And this is where WooCommerce wishlist email automation gets interesting.

If you’re already using Mail Mint, you already have the automation part covered. What you need is a way to tell Mail Mint that someone just added, removed, or saved a wishlist item.

That’s exactly what the free SaveTo Wishlist plugin does.

It comes with a built-in Mail Mint integration that turns those wishlist actions into tags. Mail Mint can then use those tags to trigger follow-up emails and other automations.

No code. No API key. No paid connector.

In this guide, I’ll show you exactly how the SaveTo Wishlist and Mail Mint integration works, how to set it up, and which wishlist automation you should build first.

In this guide:

• What the SaveTo Wishlist and Mail Mint integration does
• Why WooCommerce wishlist activity is worth automating
• How to set up the integration
• Which automation to build first
• Four ways to put wishlist tags to work in Mail Mint
• What the integration leaves to Mail Mint
• Frequently asked questions

Let’s start with what actually happens when a customer adds a product to their wishlist.

Here’s the fuller picture, starting with what this integration guarantees you.

Now let’s open up the mechanism itself, since knowing exactly what fires and when is what makes the rest of this useful.

How Mail Mint Turns A Wishlist Save Into An Automated Email

Mail Mint doesn’t know anything about wishlists on its own, and it doesn’t need to. SaveTo Wishlist listens for three wishlist events and hands Mail Mint a tag for each one.

That’s the whole mechanism, and it’s deliberately small.

When a logged-in customer adds a product, removes one, or saves a wishlist, SaveTo Wishlist fires. It first creates or updates their Mail Mint contact, then assigns a tag that matches the event.

Wishlist event	Tag applied in Mail Mint
Product added to a wishlist	Wishlist – Product Added
Product removed from a wishlist	Wishlist – Product Removed
Wishlist saved	Wishlist – Saved

You don’t create these tags yourself. SaveTo Wishlist creates each one the first time its event fires.

New contacts arrive with the customer’s first name, last name, and email address, at subscribed status.

From there, it’s entirely a Mail Mint job. Tag Assigned is one of Mail Mint’s standard triggers, so a wishlist action starts an automation exactly the way any other tag does, inside the same automation canvas you already build everything else in.

There’s nothing new to configure on the Mail Mint side.

Two things worth knowing about how it runs

• There is no configuration screen. SaveTo Wishlist has no Mail Mint settings tab and no API key field. Both plugins active is the whole setup.
• Everything happens on your server. The sync calls Mail Mint’s own contact functions on the same WordPress install. No outbound request means no third-party endpoint to wait on.

And when Mail Mint isn’t active, SaveTo Wishlist registers no wishlist hooks at all. The bridge costs nothing, in setup time or performance, on stores that don’t use it. That’s the mechanism. Next is why it’s worth pointing Mail Mint at in the first place.

Why WooCommerce Wishlist Activity Is Worth Automating

Most abandonment isn’t a checkout problem. It’s a timing problem, and wishlist data is the clearest record of it you’ll get.

Baymard Institute has tracked the global average cart abandonment rate for 14 years. It currently sits at 70.19%.

The more useful number sits inside that figure. In Baymard’s abandonment-reasons research, 42% of US online shoppers said they abandoned because they were “just browsing” or not ready to buy yet.

Baymard treats that group as largely unavoidable. It isn’t friction you can design away, because those shoppers were never going to convert on that visit regardless of your checkout flow.

That’s precisely the group a wishlist captures, and it’s the group email was built to reach. Litmus puts email’s average return at $36 for every dollar spent, one of the highest of any marketing channel.

A wishlist tag gives Mail Mint somewhere specific to point that return.

What the tag tells you that a purchase doesn’t

Purchase history tells you what someone already owns. A wishlist save tells you what they still want.

Those are two different lists, and the second one is the one worth emailing.

A wishlist save is also more deliberate than most signals you collect. A page view can be an accident or a bounce.

Saving a product takes a click and, in most stores, a logged-in account, which makes it a sturdier basis for segmenting customers than browsing data ever is.

In practice, wiring the two together comes down to four concrete gains.

• Segments that build themselves. Your interested-but-not-bought list grows on its own, with no manual list hygiene.
• Timing you didn’t have before. The tag lands at the moment of interest, not on your newsletter’s schedule.
• New contacts from traffic you already have. A logged-in customer who saves a product becomes a subscribed Mail Mint contact, with no extra opt-in form required.
• No data leaving your site. The whole sync runs locally, which is a shorter conversation with your privacy policy than a third-party wishlist-to-email connector would be.

Those are the reasons to bother. Here’s exactly how to turn it on.

How To Set Up The Integration

There’s nothing to configure, so setup really means two things. Confirming the sync runs, and building your first automation.

Before you start, you’ll need

• Mail Mint installed and active. Grab the free version if you don’t have it yet.
• SaveTo Wishlist installed and active. The free version covers this integration in full.
• A test customer account you can log in with.

That last item matters more than it looks. The sync only runs for logged-in customers, because a Mail Mint contact needs an email address to exist.

Step 1: Generate a wishlist event

Log in to your store as the test customer, then add one product to a wishlist. That single action creates the contact and the first tag.

Step 2: Confirm the tag in Mail Mint

In your WordPress admin, go to Mail Mint → Contacts → Tags. You should see Wishlist – Product Added in the list.

Open the test customer’s record and confirm the tag is attached to them.

Step 3: Build the automation

From the Mail Mint dashboard, open the Automation tab and click New Automation. Then pick Tag Assigned as your starting point, then select the wishlist tag you want to react to.

Add your steps after that. A Time Delay followed by Send an Email is the simplest useful version.

Later, you can grow it with conditions, sequences, or an outgoing webhook.

For the full click-by-click walkthrough with screenshots, see the SaveTo Wishlist Mail Mint integration guide.

That’s the entire setup. The real decision is which automation you point it at first, so let’s settle that before getting into all four builds.

Four Ways To Put Wishlist Tags To Work In Mail Mint

Three tags is a small vocabulary, but it covers more ground than it looks like it should. These four are the best places to start, in the order most stores should build them.

1. Send a delayed nudge, not a discount

Trigger on Wishlist – Product Added, add a Time Delay of two or three days, then send one email.

Make it a reason to come back rather than a coupon, something that removes the specific hesitation that made them save instead of buy. That reason changes by product type, so here’s what it looks like in practice.

Whatever you choose, the one thing to avoid is leading with a discount.

Discount-first is the reflex, and it’s usually the wrong one. It teaches your most engaged customers to wait for a coupon on things they already wanted.

If drafting that email is the part you keep putting off, this is exactly the kind of one-off copy Mail Mint’s AI Email Engine (Pro) is built for. Describe the reason you want to give and review the draft it hands back, instead of starting from a blank editor.

2. Treat a saved wishlist as your highest-intent segment

Saving an entire wishlist is a bigger commitment than saving one product. Someone doing that is planning, not browsing.

Use Add to List(s) inside the automation to push those contacts onto a dedicated list, then send them new-arrival and restock announcements first.

It’s the cheapest early-access tier you’ll ever build, because the list built itself.

3. Use the removal tag as a suppression signal

This is the tag most stores skip, and it’s the one that protects your sender reputation. A removal usually means the customer bought elsewhere or lost interest.

Trigger on Wishlist – Product Removed, then use Remove Tag(s) to strip the added tag.

Stop Automation works too, if you need to pull someone out of an in-flight sequence.

4. Pin your tag names before you build anything on top of them

The default tag titles are translated strings. A site running a different admin locale can produce differently named tags without you changing anything.

On multilingual stores, a developer can pin the names with the stwlite_mailmint_event_tags filter.

The same applies if you want tag names that match your existing Mail Mint naming convention. Decide that before your automations depend on the default names.

Start with one of these four, measure it, then add the next. Building all four at once is how automations end up shipped and never checked.

Those four cover behavior. Here’s exactly where this integration stops, and what Mail Mint picks up instead.

What The Integration Leaves To Mail Mint

SaveTo Wishlist keeps this bridge deliberately light. It sends the event and nothing more.

Knowing exactly where it stops saves you from building an automation that can’t work, and in every case, Mail Mint already covers the rest of the ground.

It sends behavior, not product details

No product name, SKU, price, or quantity crosses over. Only the tag does.

That’s what keeps the sync local and instant.

For campaigns that need order or catalog data (a price-drop alert, a post-purchase upsell, a review request), reach for Mail Mint’s native WooCommerce triggers instead.

That set includes Product Ordered, Order Completed, Review Received, and a Price Dropped / On Sale trigger that fires when a product’s sale price is set or updated.

The wishlist tags cover behavior. Those triggers cover the catalog.

Between the two, you can run wishlist follow-up and order-based automation from the same Mail Mint dashboard, on the same free-to-start plan, without a second tool.

The tags build a history, not a snapshot

Removing a product adds the Wishlist – Product Removed tag. It doesn’t delete the Wishlist – Product Added tag.

So a contact can carry both, and what you get is a running log of what that customer did, not a live mirror of what’s currently on their wishlist.

That log is useful on its own for segmentation. If you’d rather the tags reflect only what’s currently saved, add a Remove Tag(s) step to your automation.

Mail Mint puts that control in the builder, so the behavior is yours to choose.

Guest wishlist activity is skipped

Email automation needs an email address, and a guest hasn’t given you one. A guest save creates no contact and no tag.

If a large share of your saves come from guests, the fix sits upstream of email. Give shoppers a reason to create an account, and a saved wishlist is one of the better reasons you can offer.

Once the account exists, Mail Mint has everything it needs to pick the signal up.

That’s the full picture, from the first tag to the automations built on top of it. Here’s what to actually do with it.

Start With One Automation

Here’s what to do next:

• Activate both plugins, then confirm the tags appear under Mail Mint, Contacts, Tags.
• Decide your tag names before building anything that depends on them.
• Ship the delayed nudge first. It has the clearest payback of the four.
• Add the removal suppression next, so you stop emailing about dropped products.
• Check what the tags carry before writing copy that assumes product details.

You already own the conversion engine. Mail Mint can send the right email at the right moment, to a segment that defines itself, without you touching a list by hand.

What an engine needs is a signal. A wishlist save is one of the strongest your store produces, and at the moment it’s going nowhere.

SaveTo Wishlist is the free piece that hands Mail Mint that signal. Grab SaveTo Wishlist free, activate it next to Mail Mint, and save one product as a test customer. The tag will be waiting in your Contacts when you go and look, ready for the first automation you point at it.

Then go and build that one automation. The delayed nudge is the shortest route to a result you can measure.

Frequently Asked Questions