Turn Zapier Table records into wallet passes

• 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 — a loyalty card or a generic pass. Note its field names (e.g. points, member_id): they must match the Table fields you map.
• A Zapier account — Tables is built in, so this is the only account you need on the source side.
• A Zapier Table with the records you want to issue from, including a field for the holder's email so passes 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, choose Zapier Tables as the trigger app, and pick the trigger that fires when a record is created or updated. Select the Table Passmint should watch, then send a test so Zapier reads a sample record and learns your field names.

TODO(verify): Confirm the exact Zapier Tables trigger label (new vs. new-or-updated record) and that it asks you to choose a specific Table. Note whether updates re-fire the trigger as you intend.

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 Table fields.

In Field Values, map each Table field you want on the pass to a template field. The key on the left must exactly match a field name in your Passmint template (e.g. points → a Points field); the value on the right is the field from the record. Send a test and confirm a pass is created with the right values.

TODO(verify): Confirm the Zapier Tables field labels as the trigger exposes them, and that the Field Values keys you reference exist as field names in the real template. Mismatched keys are silently ignored.