# Turn new Clover customers into Mailchimp subscribers

> Every hour, new Clover customers with an email land in your Mailchimp audience, tagged and ready, so every walk-in signup becomes a subscriber.

- Workflow type: agent
- Services: Clover, Mailchimp
- Categories: Marketing, Operations
- Published: 2026-07-17

## What it does

- Checks Clover on an hourly schedule for customers who were just added or updated at the point of sale.
- Adds anyone with an email on file to your Mailchimp audience along with their first name, last name, and phone number.
- Tags every new subscriber with clover-import plus any loyalty tier the merchant already tracks, so you can segment them later.
- Skips customers without an email and any obvious staff or test entries, then logs everything it did so you can spot-check.

## What you'll need

- A Clover merchant account with the customers feature turned on at the register
- A Mailchimp account and the audience you want new Clover customers added to
- Optional: the loyalty tier or VIP tag names you already use in Clover, so they carry over

## Prompt

Every hour, sync brand new Clover customers into a Mailchimp welcome audience so walk-in signups at the register turn into marketable subscribers with no cashier follow-up step.

Trigger: cron, hourly. Between runs, remember the last run's high-water mark (the largest modifiedTime seen, in milliseconds) so we never re-scan the whole customer book.

Step 1 — Pull new and recently changed customers from Clover. Call the Clover List Customers operation for the connected merchant with a filter of modifiedTime greater than the stored cursor, and expand emailAddresses and phoneNumbers so the contact methods come back inline (Clover keeps them as separate subresources on the customer object). Page through all results, and remember the highest modifiedTime seen so the next hourly run picks up where this one left off.

Step 2 — For each returned customer, have the agent decide what to do. A Clover customer can have zero or multiple emailAddresses and phoneNumbers. Skip anyone with no email address at all. Skip obvious staff or test entries (names like "Test", "Cashier", "Owner", employee-looking emails on the merchant's own domain, single-letter names). If the customer already exists in Mailchimp (same email), treat this as an update rather than a fresh signup and only refresh the merge fields and tags. Format firstName and lastName cleanly (trim, title-case, split on space if only a single "name" field was captured) and pick the primary phone number.

Step 3 — Upsert into Mailchimp. For each surviving customer, call the Mailchimp Add or Update Member (Upsert) operation against the configured audience (list_id). Use the customer's email address as the key. Set merge fields FNAME, LNAME, and PHONE. Apply tags including "clover-import" plus any loyalty tier the merchant tracks on the customer in Clover (VIP, Gold, Silver, etc., mirrored verbatim as Mailchimp tags). Prefer upsert over Add Member so hourly re-runs are idempotent and don't error on "Member Exists".

Step 4 — Log what happened. For every Clover customer in this run, log one line: added, updated, or skipped, with the reason ("no email", "looks like staff", "already subscribed, refreshed tags", etc.) and the Clover customer id so the merchant can open them at the register to double-check. Surface a short summary at the end (added N, updated M, skipped K) so the merchant can glance at run history and know the sync is healthy.

Config the workflow should expose: the target Mailchimp audience (list_id), whether to include loyalty tags, and any custom skip rules (extra staff email domains or name patterns to filter out).

## How to customize

- Change how often it runs (every fifteen minutes, twice a day, mornings only, etc.).
- Point it at a different Mailchimp audience or swap in your own tag naming instead of clover-import.
- Adjust the rules for what counts as a staff or test entry so real customers never get filtered out.

## FAQ

### Will this create duplicate subscribers if I run it every hour?

No. The workflow upserts each customer into Mailchimp using their email address as the key, so re-running it just refreshes their name, phone, and tags instead of adding a second copy.

### What happens to Clover customers who don't have an email on file?

They're skipped and noted in the run log. They stay in Clover as usual, they just don't get added to Mailchimp until someone captures an email for them.

### Can it carry over loyalty tiers or VIP status?

Yes. The workflow reads any tags the merchant already puts on the customer in Clover and applies them alongside a clover-import tag in Mailchimp so you can build segments off them.

### Does this send the welcome email itself?

No, the sending is handled by Mailchimp. You set up a welcome journey once in Mailchimp keyed off the audience or the clover-import tag, and this workflow keeps feeding new subscribers into it.

### How do I verify which customers were added on a given run?

Each run logs the added, updated, and skipped customers so you can open the run and see exactly which walk-in signups became subscribers and which were left out and why.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-new-clover-customers-into-mailchimp-subscribers