Resources · Zapier integration

PassKit Coupons Zapier integrationAutomate PassKit Coupons with Zapier.

The PassKit Coupons Zapier integration gives you 3 triggers, 8 actions and 0 searches. All 3 triggers are instant, so a coupon issued, updated or saved to a phone wallet reaches your Zap without waiting, free plan included.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PassKit Coupons Zapier integration does for you

The PassKit Coupons Zapier integration connects your digital coupon campaigns, the passes your customers keep in Apple Wallet or Google Wallet, to the rest of your tools without code. A coupon gets issued, changed or saved to a phone, and Zapier passes it on. Or another tool tells PassKit to issue, redeem or cancel a coupon for you.

Three results worth building first. Coupons handed out by your other tools: a new sign-up or a purchase elsewhere runs Issue Coupon, and the customer gets a pass for the right offer. Redemptions recorded at the till: your point-of-sale or booking tool runs Redeem Coupon, so PassKit knows the coupon has been spent. A live view of who actually kept the offer: Coupon Installed feeds a sheet or a CRM each time a customer saves a pass to their wallet.

What Zapier does not do here. There is no search step for this app: the two Get Coupon actions fetch a record you already have the ID of, they do not hunt for one by name or email. There is no trigger for a redemption, and no action to create a campaign or an offer, which you set up in PassKit first. Nothing from before the Zap was published gets picked up either. Still choosing a platform? See the Zapier review, then Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this whole page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, like a coupon being issued in PassKit. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that issues, updates, redeems or fetches something for you in an app.
Task
The unit Zapier bills: one action your Zap completed successfully. The number on your plan counts those and nothing else.
Instant vs polling trigger
An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer that depends on your plan.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and quietly stops it otherwise.
Connection
Your PassKit account linked to Zapier once, then reused by every step of every Zap that works with PassKit Coupons.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What PassKit Coupons on Zapier really costs

Zapier bills in tasks, and only for actions that go through. Triggers never cost anything, and all three PassKit Coupons triggers are instant, so your plan's check interval does not apply.

  • Tasks on the free plan100 per month
  • Steps on the free plan2: one trigger, one action
  • Premium appNo
  • Instant triggers3 of 3

Every successful action counts one task. That includes the two Get Coupon actions: on Zapier they are actions, not search steps, so each completed lookup is billed. A failed action is not counted. The free plan gives 100 tasks a month and Zaps of two steps. A filter or a second action makes the Zap multi-step, which needs a paid plan. PassKit Coupons is not a premium app, so all of this works from the free plan.

Connect

Connect PassKit Coupons to Zapier in 3 steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, go to the Apps page and click + Add connection. In the dialog, search for PassKit Coupons by name and select it from the results.

  2. 02

    Sign in to PassKit

    Click Add connection, then sign in to PassKit in the tab that opens. Use the account that holds your coupon campaigns. If a colleague owns them, get read or write access from them before you start.

  3. 03

    Grant access

    Approve the access Zapier requests. The connection now appears on your Apps page and every PassKit Coupons step reuses it, so you sign in once instead of once per Zap.

First Zap

Your first Zap: tell the team when a coupon lands in a wallet

GoalWhen a customer saves a coupon to their phone wallet, the Zap fetches the coupon record and emails your team.

  1. 01

    Build: pick the trigger

    Create a Zap, choose PassKit Coupons and Coupon Installed. Select your connection, then the campaign the Zap should watch: the trigger needs its Campaign Id.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent installs from that campaign. Pick one so the next steps are mapped on a real coupon, not on empty sample data.

  3. 03

    Fetch the coupon

    Add Get Coupon by Id and map the coupon ID the trigger returned. This second action makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the email

    Add an email step to your team's address and write the message with details from the coupon record. Test each step once and read what came back.

  5. 05

    Publish

    Click Publish. From then on, every coupon saved to a wallet in that campaign starts the Zap. Coupons installed before that moment stay out of it.

Triggers

The 3 PassKit Coupons triggers

3 events start a Zap when something happens in PassKit Coupons, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Coupon Installed

Instant trigger

In Zapier“Triggers when a coupon is installed in the wallet. Dependent on the Pass Holder being connected to internet.”

Starts the Zap when a customer adds one of your coupons to the wallet on their phone. This is the signal that the offer was not just sent but kept, which is the number most campaigns actually care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a café wants each saved coupon logged against the campaign that brought it in.
Watch out
PassKit only learns about the install once the customer's phone is online, so an offline phone reports it later.
2

New Coupon Issued

Instant trigger

In Zapier“Triggers when a new coupon is issued for a Campaign.”

Reacts each time a new coupon is created for a campaign, whoever issued it: you in PassKit, another Zap, or another tool. It is the place to keep a single register of every coupon in circulation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
marketing wants every issued coupon copied to the CRM record of the customer who received it.
Watch out
the trigger asks for a Campaign Id, so one Zap watches one campaign; a second campaign needs its own Zap.
3

Coupon Updated

Instant trigger

In Zapier“Triggers when a new coupon is updated in a Campaign.”

Fires when a coupon of a given campaign is changed. Your other tools follow the coupon's life instead of keeping the version it had on the day it was issued.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a retailer keeps a coupon sheet in sync and wants every change reflected there.
Watch out
a Zap that runs Update Coupon in the same campaign changes a coupon, which wakes this trigger again; that loop burns tasks fast.
Actions

The 8 PassKit Coupons actions

PassKit Coupons gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Get Coupon by External Id

Action

In Zapier“Gets a Coupon record by External ID”

Fetches a coupon record from your own External ID, within the campaign you name.

When to use it
your shop or CRM knows its own reference, not PassKit's, and the Zap needs the coupon behind it.
Watch out
it is an action, not a search step, so each successful lookup costs a task.
2

Get Coupon by Id

Action

In Zapier“Gets a Coupon record”

Fetches a full coupon record from the ID PassKit gave it, the same ID used as the serial number in Apple Wallet and the object identifier in Google Wallet.

When to use it
a later step needs details the trigger did not carry.
Watch out
PassKit assigns that ID and you cannot write it, so map it from an earlier step.
3

Issue Coupon

Action

In Zapier“Issue a new coupon.”

Creates a new coupon in one of your campaigns, for the offer you pick. The customer then gets a pass ready to save to their wallet.

When to use it
a newsletter sign-up or a first order in another tool should hand out a welcome discount.
Watch out
it needs both a Campaign Id and an Offer Id, so the offer must already exist in PassKit.
4

Patch Person

Action

In Zapier“Updates personal information of a coupon holder”

Edits the personal information of a coupon holder and leaves the rest of the coupon alone.

When to use it
a customer corrects their personal details in your CRM and the pass in their wallet should follow.
Watch out
this is the safe way to touch personal details; Update Coupon can wipe them when the person fields are left blank.
5

Redeem Coupon

Action

In Zapier“Redeems a coupon by either internal PassKit ID or External ID.”

Marks a coupon as used, found either by its PassKit ID or by your own External ID.

When to use it
the till, the booking tool or the online checkout records the discount and PassKit must know it was spent.
Watch out
pick the identifier your other tool really holds; an ID mapped where the other one is expected means the coupon is not found.
6

Update Coupon

Action

In Zapier“Updates an existing Coupon. If updating only a coupon holders personal information use the Patch Person action as empty values along with an updated person field will override existing personal information.”

Changes an existing coupon in a campaign, tied to its offer.

When to use it
the details of a coupon must follow a change made in your shop or CRM.
Watch out
if you only want to change the holder's personal details, use Patch Person instead: here, empty person fields overwrite the details already on the coupon.
7

Update Coupons External Id

Action

In Zapier“Updates an existing Coupons external Id.”

Replaces the External ID of an existing coupon with a new one you provide.

When to use it
you renumber customers or orders in your own system and want coupons to carry the new reference.
Watch out
other Zaps that find coupons by External ID will look for the old value until you change them too.
8

Void Coupon

Action

In Zapier“Voids (deletes) an existing Coupon by ID or External ID. Invalidates the coupon in the customers Mobile Wallet; rendering it useless. This method is irreversible and should be used with care.”

Deletes an existing coupon by ID or External ID and makes the pass in the customer's wallet unusable.

When to use it
an order is refunded or a coupon was issued by mistake.
Watch out
it cannot be undone; test it on a coupon of your own before pointing it at customers.
When it breaks

When a PassKit Coupons Zap breaks

Zapier links no help article to PassKit Coupons, so these cases come from the general limits, read through what this app does.

Six situations explain most surprises with coupon Zaps. When none of them fits, the Zapier troubleshooting page is the next stop.

  • Coupons issued before the Zap are ignored

    A Zap only reacts to what happens after you publish it. Coupons issued, updated or installed before that are never picked up; moving that history is a separate job.

  • Update Coupon sets off Coupon Updated

    A Zap that updates a coupon in the campaign its own Coupon Updated trigger watches restarts itself on every run, and burns through the task count quickly.

  • A bulk issue is held back

    Issuing a huge batch of coupons at once, after an import or a migration, can trip Zapier's flood protection, which holds those runs back instead of firing them all.

  • Installs that arrive late

    Coupon Installed depends on the customer's phone being online. A pass saved without a connection only reaches PassKit, and your Zap, once the phone reconnects.

  • Personal details wiped by an update

    Update Coupon with blank person fields overwrites the holder's existing details. Use Patch Person when only the personal information should change.

  • A voided coupon cannot come back

    Void Coupon deletes the coupon and kills the pass in the wallet. A wrong ID mapped in the Zap means a real customer loses an offer you cannot restore.
Need help

Need help automating PassKit Coupons with Zapier?

A person reads every message.

FAQ

PassKit Coupons Zapier integration: frequent questions

01Is the PassKit Coupons Zapier integration free?
Yes, for simple Zaps. PassKit Coupons is not a premium app, so it works on the free Zapier plan, which includes 100 tasks a month. What the free plan limits is the shape: two steps only, one trigger and one action. Coupon Installed followed by one email fits. Coupon Installed, then Get Coupon by Id, then an email is three steps, so it needs a paid plan. A filter has the same effect, because it also counts as a step and makes the Zap multi-step.
02How many tasks does a PassKit Coupons Zap use?
One task for each action that completes, nothing for the trigger. A Zap that issues a coupon after each sign-up spends one task per sign-up. Add Get Coupon by Id and an email, and each run costs three. Note that the two Get Coupon actions are billed like any other action, since this app has no search steps. A failed action is not counted. Waiting for new coupons costs nothing either, however many your campaigns produce.
03Are PassKit Coupons triggers real time?
Yes. All three are instant triggers: PassKit reports the event to Zapier and the Zap starts at once, on every plan, including the free one where a polling trigger would wait up to 15 minutes between checks. A Zap built on an instant trigger shows a lightning bolt in the editor. One nuance for Coupon Installed: PassKit itself only knows about the install once the customer's phone is online, so the delay can come from the phone, not from Zapier.
04What do you need to connect a PassKit Coupons account?
A PassKit account that holds your coupon campaigns, plus read or write access to any campaign you do not own. In Zapier, open the Apps page, click + Add connection, choose PassKit Coupons, sign in in the tab that opens and approve the access. Then, before building, make sure the campaign and the offer exist: every trigger asks for a Campaign Id, and Issue Coupon and Update Coupon also ask for an Offer Id.
05Why did Update Coupon erase a customer's details?
Because Update Coupon rewrites the coupon as you send it, and person fields left empty replace the details already stored. PassKit's own description warns about it and points to Patch Person for changes that only concern the holder. So split the job: Patch Person when only personal information changes, Update Coupon when the coupon itself changes, with every person field mapped. Test on a coupon of your own before publishing, and check the pass afterwards.
06What if the PassKit Coupons operation you need is missing on Zapier?
Then the Zap cannot do it directly. The integration covers 3 triggers and 8 actions: issue, update, patch, redeem, void and fetch coupons. There is no trigger on redemption, no search step, and nothing to create a campaign or an offer. Rework the scenario around what exists, for instance fetch a coupon by External ID before acting on it, or set up campaigns and offers in PassKit by hand. The app page on Zapier lists the operations currently offered in the editor.
07Zapier, Make or n8n for PassKit Coupons?
Choose by the shape of the job, not by a ranking. On Zapier, PassKit Coupons offers 3 instant triggers and 8 actions, works on the free plan and connects with a sign-in. The trade-offs are clear: two steps on the free plan, every completed action billed, lookups included. If each Zap does one thing, such as issuing a coupon after a sign-up, that fits well. If every run chains lookups, filters and several updates, compare what the other platform offers for PassKit and how it bills a run.
Same platform

Other docs you might need on this stack.

Browse all integrations