Give every HubSpot contact a wallet membership card that tracks their tier

• A Passmint account and an API key (pmk_live… or pmk_test…), from Developers → API Keys.
• A Passmint membership or loyalty template — note its field names (e.g. member_tier, points, account_manager): they must match the HubSpot properties you map.
• A Zapier account (the free plan is enough to build and test this).
• A HubSpot account where contacts carry the properties you want on the card — lifecycle stage, a tier property, points, owner/account manager. A contact email is recommended so passes can be delivered, tracked, and found again for updates.

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 HubSpot as the trigger app. Pick the trigger that fires when a contact is created, connect your HubSpot account, and send a test so Zapier can read a sample contact and learn your property names. If you only want cards for qualified contacts, add a Zapier filter on lifecycle stage (e.g. only continue when it's Lead or Customer) right after the trigger.

TODO(verify): Confirm HubSpot's exact 'new contact' trigger label in Zapier and that the test returns the contact properties you need (email, first/last name, lifecycle stage, your tier and points properties). Note whether the trigger surfaces internal property values (e.g. lifecyclestage = 'customer') versus their display labels.

Add an action step, choose Passmint, and select Create Pass. Pick the membership or loyalty template from the dropdown — Zapier loads your templates automatically. Map Holder Email from the contact's email property and Holder Name from the contact's first and last name so the card is addressed to them and can be found again later by email.

In Field Values, map each contact property you want on the card to a template field. The key on the left must exactly match a field name defined in your Passmint template — member_tier → the tier property, points → the points property, account_manager → the contact owner. The value on the right is the property from the contact. Properties you don't map are simply left off the card.

TODO(verify): Confirm, on a real template, that the Field Values keys you reference exist as field names in that template — mismatched keys are silently ignored. Also confirm which HubSpot property holds your tier (lifecycle stage, a deal stage, or a custom property) and map that one.

Build a second Zap with a HubSpot trigger that fires when a contact property changes — point it at the tier or lifecycle-stage property. Add a Passmint Find Pass step using the contact's email as Holder Email to locate the card they already have, then add Passmint Update Pass, mapping the Pass ID from Find Pass and the new value into Field Values (e.g. member_tier → the upgraded tier). Passmint pushes the change to the installed card automatically — no re-issue, no resend.

TODO(verify): Confirm HubSpot's 'contact property changed' trigger in Zapier and that you can scope it to a specific property (e.g. lifecyclestage or your tier property). Confirm the changed value comes through on the trigger output so you can map it into Update Pass.

Run the create flow with your test contact and check the card is created in Passmint with the right tier. Open it on a phone, then change that contact's tier property in HubSpot and confirm the sync flow updates the same card in your wallet. When both look right, switch your API key to pmk_live…, turn the Zaps on, and watch a real contact flow through.