Keep your membership directory, loyalty base, or partner roster in Airtable; let each record become a live Apple Wallet or Google Wallet pass — issued automatically, and updated in place when the record changes.
A few ways teams put Airtable and Passmint to work together.
One Zap links the two — live in a few minutes, no code involved.
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 Airtable as the trigger app. Pick the trigger that fires when a record is created, then select the base and table Passmint should watch. If your records only become pass-worthy once they're approved or active, point the trigger at a filtered view instead of the whole table — that way only records that appear in that view will fire the Zap. Send a test so Zapier can read a sample record and learn your field names.
TODO(verify): Confirm the exact Airtable trigger label for a newly created record and that it asks you to choose a base + table (and, ideally, lets you scope to a specific view). Note which field types it exposes cleanly in the sample (single-select, linked records, attachments, formula/rollup fields often need special handling).
Add an action step, choose Passmint, and select Create Pass. Pick the template to issue from the dropdown — Zapier loads your templates automatically. Then map Holder Email and Holder Name from the matching fields on the Airtable record.
In Field Values, map each Airtable field you want on the pass to a template field. The key on the left must exactly match a field name defined in your Passmint template (e.g. member_tier → your Tier single-select, points → your Points number); the value on the right is the field from the record. Watch the typed fields: a single-select comes through as its option text, a linked-record field usually arrives as the linked record's name or ID, and a rollup/formula arrives as its computed value — map whichever form your template expects. Fields you don't map are simply left off the pass.
TODO(verify): On a real template, confirm the Field Values keys you reference exist as field names in that template (mismatched keys are silently ignored). Also confirm how Airtable's typed fields surface in Zapier — single-select option text vs. ID, and whether linked-record fields come through as names or record IDs.
Add a second Airtable action that updates the same record, and map Passmint's Pass URL output into a URL field (e.g. 'Wallet link') on that record. Now every record carries its own shareable pass link right next to the data it was issued from — handy for a manual send, a mail merge, or an Airtable button field that opens the pass.
TODO(verify): Confirm Airtable's 'update record' action and that it can target the record from the trigger using its record ID (the trigger should expose the record ID to pass through). Confirm a URL field accepts the mapped pass URL.
Run the Zap with your test record and check that a pass is created in Passmint and the URL comes back. Open the pass on a phone to confirm it looks right, then switch your API key to pmk_live…, turn the Zap on, and add a record (or move one into your watched view) to see it work end to end.
The details teams check before switching the Zap on.
Free for your first passes. No Apple or Google certificates to manage, no code to write.