Connect Passmint to your tools with Zapier

Zapier connects Passmint to thousands of other apps without any code. When something happens in one of your tools — a ticket sale, a new signup, a form submission — Zapier can have Passmint issue, update, or void a pass automatically. And when something happens to a pass, Passmint can kick off a Zap in any of your other apps.

This page is the full reference for the Passmint Zapier app: how to connect it, every action and trigger it offers, and how to test and troubleshoot your Zaps.

How Passmint works with Zapier

A Zap has two halves: a trigger (something happens) and one or more actions (do something in response). Passmint plugs into both sides.

• Use Passmint as an action to issue, update, void, or find a pass in response to an event somewhere else (for example, "when a Stripe payment succeeds, create a pass").
• Use Passmint as a trigger to start a Zap when pass activity happens (for example, "when a pass is installed, add a row to Google Sheets").

Before you start

You'll need a Passmint API key to connect the app.

Connect your Passmint account

The first time you add Passmint to a Zap, Zapier asks you to connect an account.

The environment (test vs live) is determined by which key you connect, so a Zap built on a test connection issues only test passes until you swap in a live connection.

Actions — Passmint as the action

These are the things Passmint can do when a Zap runs.

Create Pass

Issues a new wallet pass from one of your templates and returns a shareable pass URL.

• Template (required) — the Passmint template to issue from. Zapier loads your templates in a dropdown, so there are no IDs to copy.
• Holder Email — the recipient's email. Optional, but it powers pass delivery and per-holder analytics.
• Holder Name — the recipient's full name, shown on the pass wherever your template references it.
• Field Values — key–value pairs mapped onto the pass. Keys must match the field names defined in your template, or they're ignored.
• Metadata — arbitrary JSON kept for your own bookkeeping. Never shown to the holder.

The step returns the new pass's ID (starts with pass_) and its shareable URL, which you can use in later steps of the same Zap.

Update Pass

Updates a pass's field values or metadata and pushes the change to every installed wallet automatically.

• Pass ID (required) — the pass to update (starts with pass_). Usually mapped from a Find Pass step or an earlier Create Pass.
• Field Values — only the fields you provide change; everything else is left alone.
• Metadata — metadata to merge onto the pass.

Void Pass

Voids a pass. Voided passes are marked invalid in installed wallets and can't be updated.

• Pass ID (required) — the pass to void (starts with pass_).

Find Pass

Finds an existing pass by holder email or pass ID — the first half of a find-and-update flow.

• Holder Email — returns the most recent pass issued to this email.
• Pass ID — look up an exact pass. Takes precedence over holder email.

Pair Find Pass with Update Pass or Void Pass to change a pass you issued earlier without storing its ID yourself.

Triggers — Passmint as the trigger

These events start a Zap. Map their output into any downstream app.

• New Pass Installed — a pass is added to someone's Apple Wallet or Google Wallet.
• Pass Updated — a pass's fields change and the update is pushed to installed wallets.
• Pass Landing Page Viewed — someone opens a pass's public landing page.
• Pass Downloaded — a pass file is downloaded, usually right before it's added to a wallet.
• Pass Removed From Wallet — a holder deletes the pass. A useful churn signal.
• Pass Voided — a pass is voided via the API, the dashboard, or a delete action.

Each trigger delivers the pass's ID, template, holder details, and the event timestamp, so you can route the right passes to the right place downstream.

Mapping template fields

For Create Pass and Update Pass, the Field Values input maps your incoming data onto the pass. The keys you provide must match the field keys defined in your template exactly — a mismatched key is silently ignored, which is the most common reason a value doesn't appear on the pass.

You can find your template's field keys in the template editor. When in doubt, run the Zap once in test mode and check the resulting pass to confirm every value landed where you expected.

Testing your Zap

Example automations

• Sell a ticket, issue a pass — Stripe (or your checkout) triggers Create Pass from your event template, then emails the holder the pass URL.
• Keep a membership in sync — when a CRM record changes, Find Pass by email, then Update Pass so the wallet card always shows the current tier or balance.
• Handle a refund — when a refund is issued, Find Pass by email, then Void Pass so the wallet card is invalidated automatically.
• Track installs — the New Pass Installed trigger logs each install to Google Sheets, Slack, or your analytics tool.

For ready-made recipes with specific apps, see popular integrations.

Troubleshooting

• A field isn't showing on the pass — the key in Field Values doesn't match a field key in your template. Keys must match exactly; unmatched keys are ignored.
• The Zap issued a test pass instead of a real one — the Zap step is using a pmk_test_ connection. Switch the step to a pmk_live_ connection.
• "Pass not found" from Find Pass — no pass matches that email or ID in the connected environment. Remember test and live passes are separate: a test key can't find a live pass and vice versa.
• Authentication failed — the API key was revoked or copied incompletely. Create a fresh key in Developers → API keys and reconnect.

Going further

Need more than the four actions above — bulk issuance, custom logic, or events Zapier doesn't cover? Passmint has a full REST API and signed webhooks:

• API reference — issue and manage passes directly.
• Webhooks — subscribe to the full set of pass events with signature verification and retries.
• API keys: test vs live — how environments work.