When a customer record is deleted in StoreHippo, remove the contact from Mailchimp

When you delete a customer record in StoreHippo, this workflow archives the matching contact in your Mailchimp audience, so people you remove from your store stop sitting on your mailing list.

StoreHippo

Mailchimp

Download this workflow Browse more workflows

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

What this workflow does

Deleting a customer in your store doesn't touch your email list. The same person stays in Mailchimp and keeps receiving campaigns until someone remembers to remove them by hand. This workflow carries the deletion across for you.

The StoreHippo trigger, Customer Deleted, fires when a customer record is deleted in your store. FlowMattic receives the customer data StoreHippo sends with that event. The Mailchimp step, Archive Member, then archives that person in the audience you choose. You map the customer's email address from the trigger so Mailchimp knows which member to archive.

Archiving is not a permanent delete. Mailchimp keeps the member's data, but they no longer count toward your audience size, and you can restore them later. If the email isn't in that audience, Mailchimp returns an error for that run, and Task History shows it on the Mailchimp step.

Honouring a customer's deletion request

A shopper asks you to remove their account. You delete them in StoreHippo, and the workflow takes them out of your active Mailchimp audience in the same move.

Clearing out test and duplicate accounts

When you delete test customers or duplicates from StoreHippo, their addresses come off your Mailchimp audience too, so they stop receiving campaigns.

Keeping audience size in line with the store

Archived members don't count toward your Mailchimp audience size, so the list tracks the customers you actually keep in StoreHippo.

How this workflow runs

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

Step 1Trigger
StoreHippo Customer Deleted
Fires when a customer record is deleted in your StoreHippo store. The customer data StoreHippo sends with the event, including the email address, is passed on for mapping.
Step 2Action
Mailchimp Archive Member
Archives the member in the Mailchimp audience you pick. Map the deleted customer's email from the trigger and connect your Mailchimp account when you import the workflow.

What you need

FlowMatticCore
StoreHippo AccountAccount
Mailchimp AccountAccount

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.

After import, delete a test customer whose email is already in your Mailchimp audience. That captures the StoreHippo fields and lets you confirm the right member is archived.
If you want the person gone for good rather than archived, swap the step for Mailchimp's Delete List Member action. Archiving can be undone, deleting cannot.
Add a Filter after the trigger that continues only when the email field is not empty, so customer records without an address don't produce Mailchimp errors.

Questions about this workflow

Does this delete the person from Mailchimp permanently?

No. Archive Member keeps their data in Mailchimp but removes them from the active audience. You can restore an archived member later.

What if the deleted StoreHippo customer was never in my Mailchimp audience?

Mailchimp has no member to archive, so it returns an error for that run. Task History shows the response on the Mailchimp step. Nothing else in your audience changes.

Will customers deleted in StoreHippo before I set this up be archived?

No. The trigger reacts to deletions as they happen. Contacts for customers removed earlier stay in Mailchimp until you archive them yourself.

Which Mailchimp audience is the person archived from?

Only the audience selected in the Archive Member step is affected. If you keep customers in more than one audience, add another Archive Member step for each extra audience.