Guide

How to create Apple Wallet and Google Wallet passes with Zapier

Zapier connects WalletPassBuilder to the apps you already use. A new customer in your store, a form sign-up or a row in a spreadsheet can give that person their own Apple Wallet and Google Wallet card, with no one copying details across. The same connection keeps cards up to date, sends lock-screen messages, and tells your other apps when someone saves a pass or joins your loyalty program.

Last updated October 17, 2026. Facts about Apple Wallet and Google Wallet were checked against Apple’s and Google’s own documentation, linked in the sources.

The short answer

In WalletPassBuilder, design a pass with @variables such as @name, so each person gets their own card.
In Zapier, add WalletPassBuilder (it's in beta, so use this invite link) and connect your account.
Build a Zap: your app’s trigger, such as a new customer or form entry, then WalletPassBuilder’s Issue a Card to a Person.
Send the card link the step returns to the person, by email or text.

You need a WalletPassBuilder account (new accounts get free pass credits to start) and a Zapier account.

What WalletPassBuilder adds to Zapier

Step	What it does
Trigger: Pass Saved to Wallet	Starts a Zap when someone adds one of your passes to Apple Wallet or Google Wallet
Trigger: Pass Removed From Wallet	Starts a Zap when someone removes one of your passes
Trigger: New Loyalty Member	Starts a Zap when a customer joins your loyalty program, with their phone number and sign-up answers
Action: Issue a Card to a Person	Gives someone their own card from a per-person pass and returns their link
Action: Update a Person's Card	Changes details on one person's card, such as points or tier; it updates on their phone
Action: Send a Lock-Screen Notification	Messages everyone who saved a pass, now or at a scheduled time
Action: Add a Loyalty Stamp or Purchase	Records a visit on a customer's loyalty card
Search: Find a Person's Card	Finds a card by the key you issued it with, or by a field such as email

1. Make a per-person pass

Issuing cards from Zapier starts from a pass you design once. Put @variables where each person’s details go: @name as the card title, @member_id in a field and as the barcode, @points or @tier wherever they belong. Every variable becomes a box to fill in the Zapier step.

Start from the Personalized pass template in the builder, which already uses @name and @tier, or see how to make QR code membership cards for a fuller example.

2. Connect WalletPassBuilder to Zapier

Open the WalletPassBuilder invite link and accept it. This adds the integration to your Zapier account while it’s in beta.
In Zapier, click Create, then Zaps, and add a WalletPassBuilder step.
Click Sign in. WalletPassBuilder opens in a window: sign in, or create an account, and click Approve.

3. Issue a card when someone signs up

Pick the trigger from the app where people arrive, such as a new order or customer in your store, a new entry in a form, or a new row in a spreadsheet. Then add Issue a Card to a Person:

Pass: your per-person pass. Only passes with @variables are listed.
Unique Key: something that identifies the person, usually their email or customer ID. If a card already has this key, the step updates that card instead of adding a duplicate, so a Zap that runs twice for the same person is harmless.
One box per @variable: map their name, member number and so on from the trigger. A new card needs every variable filled in.

The step returns the new card’s Card ID and Card Link. The link opens a page that adds the card to Apple Wallet on an iPhone or Google Wallet on Android.

4. Send each person their link

WalletPassBuilder doesn’t email the link from Zapier, so add a step that sends it: your email tool, Gmail, an SMS app, or your CRM’s welcome sequence. Map Card Link into the message, for example “Add your membership card to your phone: [Card Link]”. A Zap with this extra step is multi-step, which needs a paid Zapier plan; on Free, save the link to your CRM or spreadsheet instead and send it from there.

5. Keep cards up to date

A saved card isn’t a snapshot. Update a Person’s Card changes only the values you fill in, such as points, tier or renewal date, and the card updates on their phone. Pick the person from the Card list, or map the Card ID you saved when you issued it.

If you don’t have the Card ID, put Find a Person’s Card first and search by the unique key or by a field such as email. Tick its create a card if it doesn’t exist yet box and it issues one when the person doesn’t have a card. Updates and searches don’t use pass credits.

6. React to saves and loyalty sign-ups

WalletPassBuilder’s triggers send what happens on customers’ phones to your other apps:

Pass Saved to Wallet and Pass Removed From Wallet include the pass, the business name, the wallet (Apple or Google) and when it happened.
New Loyalty Member includes the customer’s phone number, what they typed into your sign-up form, their card link and their progress. Narrow it to one program, or leave it on all of them.

Pair New Loyalty Member with Add a Loyalty Stamp or Purchase to give every new member a welcome stamp. See loyalty cards for small businesses for setting up the program itself.

Zaps worth building

Membership card for every new member

Form or checkout sign-up → Issue a Card to a Person (unique key: email) → email the Card Link.

Loyalty card for every store customer

New customer in your store → Issue a Card to a Person with their name and customer ID → add the link to their welcome email.

Points that follow purchases

New order → Find a Person’s Card by email → Update a Person’s Card with their new points total.

New members into your mailing list

New Loyalty Member → add the contact to your email or SMS list with their sign-up answers.

A weekly lock-screen message

Schedule (every Friday) → Send a Lock-Screen Notification, such as this weekend’s special. Keep messages rare and useful; our wallet pass notifications guide covers what works.

Zapier plans and timing

Free: two-step Zaps (one trigger, one action). Zapier checks WalletPassBuilder’s triggers every 15 minutes.
Paid plans: Zaps with several actions, or with a search step such as Find a Person’s Card. Triggers are checked every 2 minutes on Professional and every minute on Team and Enterprise.

Zapier’s plans can change, so check its pricing page for the current details.

What it can’t do

Design a pass. Make it in the builder first; Zapier issues and updates cards from it.
Tell you which person saved a per-person pass. Pass Saved to Wallet reports the pass and the wallet, not the person.
See or change your billing, API key, team or password.

Frequently asked questions

Can Zapier create Apple Wallet passes?+

Yes, with WalletPassBuilder. Its Issue a Card to a Person action gives someone their own Apple Wallet and Google Wallet card from a pass you designed, and returns a link that adds it to their phone. You can run it from any of the apps Zapier connects, such as a form, a store or a spreadsheet.

Does each new customer get their own card?+

Yes. Design one pass with @variables such as @name or @member_id, and each run of the Zap fills them in for one person and gives that person their own link. Give the step a unique key, such as their email, and running it again for the same person updates their card instead of making a second one.

Do I need a paid Zapier plan?+

Not for two-step Zaps: one trigger and one WalletPassBuilder action work on Zapier's Free plan. Zaps with more than one action, or with a search step such as Find a Person's Card, need a paid Zapier plan. Your WalletPassBuilder pass credits work the same either way.

How quickly do Zaps run?+

WalletPassBuilder's triggers are polling triggers, so Zapier checks for new saves and sign-ups on a schedule set by your Zapier plan: every 15 minutes on Free, every 2 minutes on Professional and every minute on Team and Enterprise. Actions run as soon as the trigger fires.

Does it use pass credits?+

Issuing a new card uses pass credits, the same as adding a person in the dashboard. Updating a card, finding one and sending a notification don't.

Can I use it without Zapier?+

Yes. Everything the Zapier steps do is in WalletPassBuilder's REST API, and the dashboard's own automations can receive webhooks from tools like Typeform, Stripe and Square directly. Zapier is the easy route when the tool you use isn't one of those, or when you want to send the link through another app.

Sources

Apple’s newer developer pages load dynamically, so where a number comes from Apple it is taken from its Wallet Developer Guide and support pages. If Apple’s or Google’s current documentation differs, follow theirs.