Resources · Make integration

PassKit Make integrationAutomate PassKit with Make.

Loyalty cards, coupons and tickets that update themselves when something happens elsewhere. The PassKit Make integration gives you 32 modules, including 5 instant triggers. This guide shows how to link your account and build a first scenario step by step.

Try the PassKit integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PassKit Make integration do for you?

The PassKit Make integration lets PassKit talk to your other tools without code. You build a scenario, the automation Make runs for you, out of modules: bricks that each watch, create, search or update one thing in PassKit, such as a member, a coupon or a ticket.

Reward the members who add the card. Watch Installed Passes starts the scenario when someone saves their pass to a phone, and Earn Points credits a bonus on the spot. Burn Points and Set Points cover the other side, when a reward is spent or a balance needs correcting.

Issue passes from your sign-up flow. A form, a shop or a CRM hands over a new customer, Create a Member issues the loyalty pass, then Send Welcome Email reaches that record. Event teams do the same with Create a Ticket by Event ID, and marketers with Create a Coupon for a single use offer.

Keep your other systems honest. Watch Deleted Records and Watch Uninstalled Passes tell you when a member leaves or removes the pass, so a spreadsheet or a CRM can be tidied up without anyone checking by hand.

One limit to know up front: Make says its PassKit documentation is incomplete, because too little public information exists about the app. Test each module with Run once before relying on it, and keep Make troubleshooting close. If you are weighing tools, the n8n vs Make comparison lists the criteria, and the Make training walks through scenarios from scratch.

Connect

How do you connect PassKit to Make?

  1. 01

    Add a PassKit module

    Open a scenario, click the +, type PassKit and pick any module. Make then asks for a connection: your PassKit account linked to Make once, and reused by every PassKit module you add later. Click Create a connection.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off if you run two PassKit programs, say a loyalty scheme and an events account. A clear name tells you at a glance which account a module is using.

  3. 03

    Authorize and save

    Follow what PassKit asks for: either approve Make on the PassKit page that opens, or paste the key PassKit gives you. Then click Save. The module now lists what it can read from your account.

First scenario

Your first scenario: points for every installed pass

GoalWhen a member installs their PassKit pass on a phone, Make credits welcome points to that member.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add Watch Installed Passes

    Search PassKit, pick Watch Installed Passes and choose your connection. It is an instant trigger, marked with a lightning badge: PassKit calls Make through a webhook as soon as a pass lands on a device.

  3. 03

    Add Earn Points

    Click the + to the right of the trigger and add Earn Points. Map the member identifier from what the trigger sent (Run once shows you what it holds), then enter the amount to add. Each item passed along is a bundle, here one installed pass.

  4. 04

    Test with Run once

    Click Run once, then install a test pass on your own phone. Open the bubbles on each module to read the bundle it received and confirm the points reached the right member.

  5. 05

    Switch it on

    Once the test looks right, save and switch the scenario on. Every module that runs counts as one operation on your Make plan, so this flow uses two per installed pass.

Triggers

What can start a PassKit scenario?

5 modules start a scenario when something happens in PassKit. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PassKit as soon as it happens.

PassKit1Watch Created Records

Watch Created Records

Instant trigger

In Make“Triggers when a record of the specified PassKit object (e.g., Member, Coupon, etc.) is created.”

You get a scenario that wakes up whenever a new record appears in the PassKit object you choose, a member or a coupon for example. It is the natural entry point for anything that should follow an enrolment.

How it fires
instant, PassKit calls Make through a webhook as soon as the record is created.
When to use it
copying each new member into your CRM, or alerting the store team when a coupon is issued.
Watch out
pick the object carefully when you set it up, since the trigger only reports the type you selected.
PassKit2Watch Deleted Records

Watch Deleted Records

Instant trigger

In Make“Triggers when a record of the specified PassKit object (e.g., Member, Coupon, etc.) is deleted.”

This trigger tells your other tools that a record is gone from PassKit, so nothing downstream keeps a ghost member or a dead coupon. It watches whichever PassKit object you point it at.

How it fires
instant, PassKit calls Make through a webhook as soon as the record is deleted.
When to use it
removing the matching row from a customer sheet, or flagging the contact in your CRM as no longer enrolled.
Watch out
the record no longer exists in PassKit when the scenario runs, so rely on what the trigger sends rather than a later search.
PassKit3Watch Installed Passes

Watch Installed Passes

Instant trigger

In Make“Triggers when a pass is installed on the device.”

Here the scenario starts at the moment a person actually saves their pass to a device. That signal is stronger than a sign-up: the card is now in the wallet and ready to be used.

How it fires
instant, PassKit calls Make through a webhook as soon as the pass is installed.
When to use it
rewarding the install with Earn Points, or thanking the member in your messaging tool.
Watch out
a person can install, remove and install again, so decide whether a second install should earn a second reward.
PassKit4Watch Uninstalled Passes

Watch Uninstalled Passes

Instant trigger

In Make“Triggers when a pass is uninstalled from the device.”

You learn when someone removes the pass from their device, which is often the first quiet sign a customer is drifting away. The scenario receives that event and can act on it.

How it fires
instant, PassKit calls Make through a webhook as soon as the pass is uninstalled.
When to use it
tagging the contact for a win-back email, or logging churn in a shared sheet the marketing team reads.
Watch out
removing the pass and deleting the member are two different events, each with its own trigger, so pick the one you really mean.
PassKit5Watch Updated Passes

Watch Updated Passes

Instant trigger

In Make“Triggers when a record of the specified PassKit object (e.g., Member, Coupon, etc.) is updated.”

Whenever a record of the object you pick changes in PassKit, this trigger passes the new version to your scenario. It keeps outside tools in step with edits made directly in PassKit.

How it fires
instant, PassKit calls Make through a webhook as soon as the record is updated.
When to use it
syncing a member's new details back to the CRM after the support team fixes them in PassKit.
Watch out
if a later module in the same scenario updates that record again, you can create a loop, so never write back to the object you watch.
Modules

What can Make do in PassKit?

PassKit gives you 27 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PassKit1

Burn Points

Action

In Make“Burn points for a member (identified by PassKit ID or External ID). Deducts the amounts provided.”

Burn Points takes points off a member's balance, which is how a spent reward shows up on the card. You identify the member by PassKit ID or by External ID and give the amount to deduct.

When to use it
your till or shop confirms a redeemed reward and the card should reflect the lower balance.
Watch out
it subtracts rather than replaces; to force an exact figure, Set Points is the right module.
PassKit2

Change a Member Tier

Action

In Make“Changes the tier for a member using either their Member/Pass ID or Unique Member ID.”

Moving someone up or down your loyalty levels becomes a single step. The module finds the member by Member/Pass ID or Unique Member ID and switches their tier in PassKit.

When to use it
a customer crosses the spending threshold you track in your shop or CRM and deserves the next level.
Watch out
it changes the level only; if the upgrade also comes with a bonus, add Earn Points after it.
PassKit3

Check-In a Member

Action

In Make“Checks in a member using their Member/Pass ID or Unique Member ID.”

This records that a member has arrived, straight from another tool. Make locates the person by Member/Pass ID or Unique Member ID, so any system that knows one of those can log the visit.

When to use it
a gym, a club or a coworking space scans cards with its own app and wants the visit logged in PassKit too.
Watch out
pair it with Check-Out a Member if you track who is on site.
PassKit4

Check-Out a Member

Action

In Make“Checks out a member using their Member/Pass ID or Unique Member ID.”

The mirror of the check-in: it closes the visit for a member found by Member/Pass ID or Unique Member ID. Together the two modules let PassKit know who is on site.

When to use it
the exit gate or the front desk system signals that a member left.
Watch out
test both modules on the same dummy member with Run once, so you see the full visit from arrival to exit.
PassKit5

Create a Coupon

Action

In Make“Create a coupon record and issue a single use pass.”

You get a new coupon record in PassKit plus a single use pass the customer can add to their wallet. It turns any event in another tool into a ready-to-scan offer.

When to use it
a customer leaves a review, fills a survey or hits a birthday, and your scenario sends a one-off discount.
Watch out
the pass is single use by design, so for repeat offers create a fresh coupon each time.
PassKit6

Create a Member

Action

In Make“Creates a member and issues a membership/loyalty pass.”

Create a Member enrolls a new person and issues their membership or loyalty pass in the same move. It is the module that turns a sign-up anywhere else into a card in PassKit.

When to use it
a new customer checks out in your shop or signs up through a form, and should leave with a loyalty card.
Watch out
run a Search Member by Unique Member ID first when the same person could sign up twice.
PassKit7

Create a Ticket by Date

Action

In Make“Issue a ticket for the provided date.”

This issues a ticket tied to the date you provide, without first creating an event record. It suits dated admissions where the day is the only thing that matters.

When to use it
a booking tool confirms a visit for a given day and the guest should get a wallet ticket for it.
Watch out
when your tickets belong to an event already set up in PassKit, Create a Ticket by Event ID fits better.
PassKit8

Create a Ticket by Event ID

Action

In Make“Issues a ticket for an existing event.”

Here the ticket is attached to an event that already exists in PassKit, so every pass for that concert, match or conference shares the same event details.

When to use it
a ticketing or payment tool confirms a purchase and the buyer should receive the pass for that specific event.
Watch out
the event has to exist before the scenario runs; keep its ID somewhere your scenario can map it from.
PassKit9

Delete a Member

Action

In Make“Deletes member using either their Member/Pass ID or Unique Member ID.”

Delete a Member removes a member from PassKit, found by Member/Pass ID or Unique Member ID. Use it to honour a closure request from another system without logging in to PassKit.

When to use it
a customer asks to close their account in your CRM and the loyalty record should go too.
Watch out
treat the deletion as final and test it on a dummy member, never a real one, when you click Run once.
PassKit10

Earn Points

Action

In Make“Earns points for a member (identified by PassKit ID or External ID). Adds the amounts provided.”

Earn Points adds the amount you give to a member's balance, identified by PassKit ID or External ID. It is the everyday module of a points program.

When to use it
an order is paid in your shop, and the buyer earns points in proportion to what they spent.
Watch out
the figure is added on top of the balance, so a scenario that runs twice on the same order credits twice; test with a single bundle.
PassKit11

Make an API Call

Action

In Make“Performs an arbitrary authorised API call.”

When none of the ready modules does what you need, this one calls any endpoint of the PassKit API with the connection you already have. No second login, no separate credentials.

When to use it
an action exists in PassKit but none of the 32 modules covers it.
Watch out
you choose the endpoint and the request yourself, so keep the PassKit API reference open while you build it.
PassKit12

Redeem a Coupon

Action

In Make“Redeems a coupon using either their Coupon ID or Unique ID.”

Redeem a Coupon marks an offer as used, so the same pass cannot be cashed a second time. Make finds the coupon by Coupon ID or Unique ID.

When to use it
your checkout or point-of-sale system confirms the discount was applied and PassKit should know.
Watch out
map the ID from the order that actually used the discount, not from a list of issued coupons, or you burn the wrong one.
PassKit13

Redeem a Ticket

Action

In Make“Redeems a ticket using either their Ticket/Pass ID or Unique Ticket ID.”

This marks a ticket as used at the door, found by Ticket/Pass ID or Unique Ticket ID. It keeps PassKit aligned with whatever scanner or access tool your venue runs.

When to use it
an entry scanner outside PassKit validates a guest and the ticket should no longer work.
Watch out
test on a spare ticket with Run once, never on a pass a real guest will show at the door.
PassKit14

Send Welcome Email

Action

In Make“Sends a welcome email to an individual record”

Send Welcome Email sends PassKit's welcome message to one record, so nobody on your team has to write that first message by hand.

When to use it
right after Create a Member, or when a support agent re-enrolls someone who lost the original message.
Watch out
it targets an individual record, so a scenario that feeds it many bundles sends one email per bundle; check the count before switching on.
PassKit15

Set Points

Action

In Make“Assigns points to a member by Member/Pass ID or Unique Member ID.”

Set Points writes an exact balance on a member found by Member/Pass ID or Unique Member ID, whatever the balance was before. It is the reset button of the points program.

When to use it
another system holds the true balance, and PassKit should mirror it after an import or a correction.
Watch out
the old balance is replaced, not adjusted; for a normal purchase, Earn Points is safer.
PassKit16

Update Coupon Personal Info

Action

In Make“Updates personally identifiable information (PII) for the pass holder.”

This changes the personal details of the person who holds a coupon pass, without touching the offer itself. Name or contact changes stay attached to the right coupon.

When to use it
a coupon was issued before the customer completed their profile, and the missing details arrive later from your form.
Watch out
it works on coupon holders only; for loyalty members use Update Member Personal Info instead.
PassKit17

Update Member Expiry Date

Action

In Make“Updates the expiration date of a single member.”

Extending or shortening a membership becomes automatic: this module sets a new expiry date on one member.

When to use it
a renewal payment goes through in your billing tool and the pass should stay valid for the new period.
Watch out
it changes a single member per run, so a renewal list reaches it as one bundle per member; each counts as one operation.
PassKit18

Update Member Personal Info

Action

In Make“Updates personally identifiable information (PII) for the pass holder.”

Update Member Personal Info corrects the identity side of a loyalty member, the details that describe the person rather than their points or tier.

When to use it
a customer edits their profile in your shop or app, and the loyalty card should show the same details.
Watch out
points, tier and expiry are handled by their own modules; this one only touches personal information.
PassKit19

Update Members Pass

Action

In Make“Updates member by either internal PassKit ID or External ID”

This is the broad update for a member record, found by internal PassKit ID or External ID. It fits changes that do not have a dedicated module of their own.

When to use it
your CRM changes a field on the member that neither the points, the tier nor the personal info modules cover.
Watch out
reach for the dedicated modules first; they make the scenario easier to read when someone else opens it.
PassKit20

Update Ticket

Action

In Make“Updates an existing Ticket”

Update Ticket edits a ticket that already exists, so a change of plan does not force you to cancel and reissue.

When to use it
a booking changes in your reservation tool and the pass in the guest's wallet should follow.
Watch out
for the holder's name or contact details, use one of the two Update Ticket Holder modules rather than this one.
PassKit21

Update Ticket Holder Personal Info By Ticket Id

Action

In Make“Updates personally identifiable information (PII) for the pass holder.”

This updates the personal details of whoever holds a ticket, finding the ticket by its ID. It is the right tool when the ticket changes hands.

When to use it
a buyer transfers a ticket to a colleague and your form collects the new holder's details.
Watch out
if your system stores ticket numbers rather than IDs, pick the By Ticket Number version to avoid a lookup step.
PassKit22

Update Ticket Holder Personal Info By Ticket Number

Action

In Make“Updates personally identifiable information (PII) for the pass holder.”

Same job as the ID version, but the ticket is found by its number. Pick it when the number is what your support tickets or order emails carry.

When to use it
a guest writes to support quoting their ticket number and asks to correct the name on it.
Watch out
map the number exactly as PassKit stores it; a typo from a customer email simply finds no ticket.
PassKit23

Search Coupon by Coupon/Pass ID

Search

In Make“Retrieves a coupon record by Coupon/Pass ID (22 characters) generated by PassKit.”

You get the full coupon record back from the 22 character Coupon/Pass ID that PassKit generates. It lets a scenario check a coupon before acting on it.

When to use it
a scan or an order carries the PassKit ID, and you want to confirm the coupon before calling Redeem a Coupon.
Watch out
a search returns zero, one or several bundles; read what came back with Run once before mapping it.
PassKit24

Search Coupon by Unique Coupon ID

Search

In Make“Retrieves a coupon record by Unique Coupon ID.”

This search finds a coupon by the Unique Coupon ID, the reference your own system chose rather than the one PassKit generated.

When to use it
your shop stores its own coupon codes and needs the matching PassKit record before any update.
Watch out
if your system only has the PassKit ID, Search Coupon by Coupon/Pass ID is the one to add.
PassKit25

Search Member by Member/Pass ID

Search

In Make“Retrieves a member record by Member/Pass ID (22 characters) generated by PassKit.”

Search Member by Member/Pass ID retrieves a member from the 22 character ID that PassKit generates. Any later module can then use the balance, tier or details it returns.

When to use it
a scanned card gives you the pass ID, and you need the member's record before deciding on a reward.
Watch out
the ID must be the one PassKit created; your own customer number goes through the Unique Member ID search.
PassKit26

Search Member by Unique Member ID

Search

In Make“Retrieves a member record by Unique Member ID.”

This one finds a member from the Unique Member ID, typically the customer reference already used in your CRM or shop.

When to use it
before Create a Member, to check whether the person is already enrolled and avoid a duplicate card.
Watch out
a search can return no bundle at all; run a test with an unknown ID to see how your scenario behaves in that case.
PassKit27

Create Image

ActionIn the docs only

Create Image is listed among the PassKit modules, but Make gives no description of it and its PassKit documentation is incomplete.

When to use it
only after testing it on its own with Run once and reading the bundle it returns, so you know what it produces.
Watch out
do not build a live scenario around it until that test tells you what goes in and what comes out.
Need help

Need help automating PassKit with Make?

A person reads every message.

FAQ

Common questions about PassKit and Make

01Is the PassKit Make integration free?
Yes, PassKit is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and allows 512 MB of data transfer. Every module that runs uses one operation from your monthly allowance. Paid plans lift the active scenario limit and bring the minimum interval down to 1 minute. The price of PassKit itself is a separate matter.
02What do you need to connect PassKit to Make?
A PassKit account and a Make account. Make's documentation lists no prerequisites for PassKit and no dedicated setup steps, so the standard flow applies: add any PassKit module, click Create a connection, optionally name it, then approve Make on the PassKit page or paste the key PassKit provides, and click Save. The same connection then serves all 32 modules, including the API call module. If the connection ever stops working, open it from any PassKit module and repeat the same steps.
03Do PassKit triggers in Make fire in real time?
Yes. All 5 PassKit triggers are instant: PassKit calls Make through a webhook as soon as a record is created, deleted or updated, or when a pass is installed or removed from a device. You do not wait for a polling interval, unlike a scheduled trigger that Make checks on the scenario's schedule. Each event still costs one operation per module that runs, so keep an eye on busy programs.
04What if a PassKit module is missing in Make?
Use Make an API Call. It reaches any endpoint of the PassKit API with the connection you already set up, so you are not limited to the 32 listed modules. Keep in mind that Make describes its PassKit documentation as incomplete, and that Create Image has no official description, so test every module with Run once and read the bundles it returns before switching a scenario on. For recurring errors, the Make troubleshooting guide on this site covers the usual causes step by step.
05Should you use Make or n8n for PassKit?
It depends on what you already use. In Make, PassKit comes with 32 ready modules, 5 instant triggers and an API call module for the rest, all usable from the Free plan. Many apps also have an n8n node, so check whether PassKit has one and what it covers before choosing. The deciding criteria are the modules you need, your plan and the tool your team already knows. Whichever tool you pick, start with one small scenario and test it before adding more.
Same platform

Other docs you might need on this stack.

Browse all integrations