- Home
- Resources
- Integrations
- Passmint
Passmint Zapier integrationAutomate Passmint with Zapier.
The Passmint Zapier integration gives you 5 triggers, 3 actions and 1 search to issue, update and void mobile wallet passes from your other tools, and to hear back when holders download, install or delete them. What each one does, what it costs, where it breaks.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the Passmint Zapier integration actually does
It connects Passmint, the platform where you design mobile wallet passes, send them out and keep them current, to the rest of your stack through Zapier. A sale, a booking or a sign-up somewhere else can issue a pass; a holder installing or deleting that pass can update a CRM, a sheet or a support queue.
Three outcomes cover most builds. Passes issued without a dashboard: Create Pass turns a new customer in another tool into a pass, and hands back a link to share with them. Passes that stay true: Update Pass changes field values and pushes the change to every wallet where the pass is installed, so a new date or balance reaches the phone. A wallet you can see into: Pass Downloaded, New Pass Installed and Pass Removed From Wallet show where each holder stands, from the landing page to the phone and sometimes out again. Each of the three rests on one operation, so each fits in a two-step Zap.
What Zapier does not do here: nothing that happened before you publish a Zap is replayed, and a voided pass cannot be brought back or edited. Zapier also lists Passmint as a beta app, and the editor offers exactly these 9 operations (read on 2026-10-14, version App240578CLIAPI@1.0.0). If you are weighing tools, see n8n vs Zapier and Make vs Zapier.
Zapier vocabulary in one minute
Eight words come back all through this page. Here they are in plain English, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a pass being downloaded, installed or changed.
- Action
- What the Zap does after it starts: the step that writes, sends or changes something for you, such as issuing a pass.
- Task
- What Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those, nothing else.
- Instant trigger
- A trigger the app reports itself: Passmint calls Zapier the moment the event happens, so nothing waits for a scheduled check.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. No Passmint trigger works that way.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What it really costs in tasks
The trigger costs nothing. Each action that goes through costs one task, and one that fails is not counted. A three-action Zap eats three times what a one-action Zap eats.
- Trigger0 tasks, whatever the volume
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
Passmint is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, but two steps per Zap, one trigger and one action. Add Find Pass, a filter (a step that lets the Zap go on only when your condition is met) or a second action and the Zap needs a paid plan. The grid below is how often Zapier checks polling triggers; all five Passmint triggers are instant, so it never slows them down, whatever your plan. One action after each Passmint event is all the free plan allows.
Connect your Passmint account in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Passmint account linked to Zapier once, then reused by every step that uses the app.
- 02
Pick Passmint
Type Passmint in the search box of the dialog, select it and click Add connection. You need a Passmint account, plus access to any pass or template you do not own yourself.
- 03
Sign in and grant access
A new tab opens on Passmint. Sign in with the account that holds your templates and grant Zapier access. The connection then shows up in your list, ready for any Zap.
Your first Zap: greet every holder who installs the pass
GoalWhen a holder adds the pass to their wallet, look it up and write the holder's name into one of the pass fields.
- 01
Build the trigger
Pick Passmint as the app and New Pass Installed as the event, then choose your connection. No setting stands between you and the test.
- 02
Test it on a real install
Run the test. Zapier brings back the three most recent items of the connected account; pick one, so every later step is mapped on a real pass instead of blanks.
- 03
Add Find Pass
Add the search Find Pass and map the pass ID from the trigger. It returns the holder's name and email, the status and the wallet links.
- 04
Add Update Pass
Add Update Pass, map the same pass ID and put the holder's name in a field of your template. A search plus an action makes a multi-step Zap, so this one needs a paid plan.
- 05
Test, then publish
Test each step and read what came back. Then click Publish to switch the Zap on. The Zapier training covers longer builds step by step.
Passmint triggers
5 events start a Zap when something happens in Passmint, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
Pass Downloaded
Instant triggerIn Zapier“Triggers when a pass file is downloaded from the public landing page. Usually means the user is about to add it to their wallet.”
Starts the Zap when someone downloads the pass file from its public landing page. That download usually means the person is about to add the pass to their wallet, so it is the earliest sign of interest you can catch.
New Pass Installed
Instant triggerIn Zapier“Triggers when a wallet pass is installed to a user's wallet”
Runs once a wallet pass actually lands in a holder's wallet. Where the download only shows intent, this is the confirmation that the card sits on the phone and will receive your updates.
Pass Removed From Wallet
Instant triggerIn Zapier“Triggers when a holder removes the pass from their wallet. Useful for churn signals and re-engagement.”
Fires when a holder deletes the pass from their wallet. Passmint itself presents it as a churn signal, and it is the moment to try to win the person back, before they forget you entirely.
Pass Updated
Instant triggerIn Zapier“Triggers when a pass's field values are updated and push notifications are sent to installed wallets.”
Catches every change of field values on a pass, at the point where Passmint sends the push notification to the wallets where it is installed. Use it to keep a record of what changed and when holders were told.
Pass Voided
Instant triggerIn Zapier“Triggers when a pass is voided - either via the API, the dashboard, or a delete action. Voided passes are marked invalid in installed wallets.”
Reports that a pass has been voided, whether from the Passmint dashboard, a deletion or another route. Installed wallets then show the pass as invalid, so this is the trigger that keeps your other records in line.
Passmint actions
Passmint gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Pass
ActionIn Zapier“Issues a new wallet pass from a template. Returns the pass URL your user can share with the holder.”
Issues a fresh wallet pass from one of your templates and gives back the pass link, ready to share with the holder.
Update Pass
ActionIn Zapier“Updates a pass's field values or metadata and pushes the change to installed wallets automatically.”
Changes the field values or the metadata of a pass, and Passmint pushes the change to the wallets where it is installed without any extra step.
pass_; map it from the trigger or from Find Pass rather than typing it.Void Pass
ActionIn Zapier“Voids a pass. Voided passes are marked invalid in installed wallets and can't be updated. This is irreversible.”
Cancels a pass for good. Installed wallets mark it invalid and it can no longer be updated.
Passmint search
1 search step looks for data that already exists in Passmint, so a later step can use it.
A search step looks something up instead of changing it. In the editor, Passmint's search sits at the bottom of the Action event list, under the SEARCH heading. Three settings decide what happens when the result is not the one you expected.
Find Pass
SearchIn Zapier“Finds a pass by its ID and returns its current details, including holder email/name, status, and wallet links. Use it after a trigger to look up the full pass.”
Looks up a pass from its ID and hands the next steps its current details: holder name and email, status and wallet links. Most Passmint triggers tell you what happened; this tells you to whom.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that rely on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Find Pass has no such variant, so on Passmint you will not see it.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When a Passmint Zap breaks
Zapier ties no help article to Passmint, so the traps below are the general ones, seen through wallet passes.
Most broken Zaps here come from how Zapier works rather than from Passmint. If a run fails and the reason is not obvious, the Zapier troubleshooting page is the next stop.
Old passes are never picked up
A Zap only reacts to what happens after you publish it. Passes issued or installed before that are invisible to it; moving them is a separate job.The Zap that feeds itself
A Zap on Pass Updated that runs Update Pass on the same pass writes where its own trigger watches, starts again and drains your task count.Bulk issues get held back
After a mass issue or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection instead of running for each pass.
Need help automating Passmint with Zapier?
A person reads every message.



