Turn new Clover customers into Mailchimp subscribers

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).