Give every new Mailchimp subscriber a wallet coupon they won't lose

• A Passmint account and an API key (pmk_live… or pmk_test…), from Developers → API Keys.
• A Passmint template for the pass you're issuing — typically a coupon pass with fields for the discount code and expiry, or a loyalty card. Note its field names (e.g. coupon_code, offer, expires): they must match the values you map from Mailchimp.
• A Zapier account (the free plan is enough to build and test this).
• A Mailchimp account with the audience you want to issue from. Subscribers need an email address on file so the pass can be delivered and tracked.

In Zapier, add Passmint as a connected app and paste your API key when prompted. Zapier verifies it against your account immediately, so you'll know the connection works before building the rest of the Zap. Use a pmk_test… key while you're setting things up.

Create a new Zap and choose Mailchimp as the trigger app. Pick the trigger that fires when someone new subscribes, then select the audience Passmint should watch. Send a test so Zapier can pull a sample subscriber and learn which fields — email, first name, merge fields — are available to map.

TODO(verify): Confirm the exact Mailchimp trigger label for a new subscriber and that it asks you to pick a specific audience. Mailchimp also exposes triggers for a new audience member and for a tag being added — note which one your welcome-offer flow should use.

Add an action step, choose Passmint, and select Create Pass. Pick your coupon template from the dropdown — Zapier loads your Passmint templates automatically. Then map Holder Email from the subscriber's email address and Holder Name from their first/last name or a name merge field.

In Field Values, map the coupon details onto the pass. The key on the left must exactly match a field name in your Passmint template (e.g. coupon_code → the code, offer → '15% off your first order', expires → the end date); the value on the right comes from the subscriber or is typed in as a fixed value. You can also map the signup source — the audience or form name — into a field so the pass reflects where they joined. Keys that don't match a template field are silently ignored.

TODO(verify): Confirm, on a real template, that the Field Values keys you reference exist as field names in that template. If you want a unique per-subscriber code rather than a fixed one, confirm where that code lives in Mailchimp (a merge field) or whether you'll generate it in an earlier Zap step.

Add a second Mailchimp action that updates the subscriber, and store Passmint's Pass URL output in a merge field (e.g. WALLETURL). Now your welcome email — or any future campaign to that audience — can drop an 'Add to Apple Wallet / Google Wallet' button using that merge tag, so subscribers who skipped the first prompt can still grab the pass.

TODO(verify): Confirm the Mailchimp 'update subscriber' action and that it can write to a custom merge field. Note that the merge field must already exist on the audience before Zapier can populate it.

Run the Zap with your test subscriber and check that a coupon pass is created in Passmint and the URL comes back. Open it on a phone to confirm the code and expiry read correctly, then switch your API key to pmk_live…, turn the Zap on, and add a real subscriber through your signup form to watch it work end to end.