Resources · Zapier integration

PassKit Event Tickets Zapier integrationAutomate PassKit Event Tickets with Zapier.

The PassKit Event Tickets Zapier integration gives you 3 triggers, 10 actions and 0 searches. All 3 triggers are instant: a ticket issued, updated or saved to a phone wallet reaches your Zap without waiting, free plan included.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PassKit Event Tickets Zapier integration does for you

The PassKit Event Tickets Zapier integration links your event productions, and the tickets your guests carry in Apple Wallet or Google Wallet, to the rest of your tools without code. A ticket is issued, changed or saved to a phone, and Zapier passes it on. The other way round, a sale or a scan in another tool can issue, check or redeem a ticket in PassKit.

Three results to build first. Tickets issued from wherever you sell: a paid order in your shop or registration form runs Issue Ticket by Event Id, and the guest gets a ticket for an event that already exists. Passes delivered without copy and paste: New Ticket Issued followed by Get Event Ticket Pass URL gives you the link to send to the guest. Doors that know who came in: your scanning or check-in tool runs Validate Ticket or Redeem Ticket, and PassKit records the entry.

What Zapier does not do here. There is no search step: the four Get actions fetch a ticket from an ID, a ticket number or an order number you already hold. There is no trigger on a redemption or a validation, no action to cancel a ticket, and nothing to create a production, a venue or a ticket design, which you prepare in PassKit. Tickets issued before the Zap was published are never picked up. 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 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 ticket 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, checks, redeems or fetches a ticket 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 your event tickets.
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 Event Tickets on Zapier really costs

Zapier bills in tasks, and only for actions that go through. Triggers never cost anything, and all three PassKit Event Tickets triggers are instant, so your plan's check interval plays no part.

  • 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, and that includes the four Get 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 Event Tickets is not a premium app, so it runs on the free plan.

Connect

Connect PassKit Event Tickets 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 Event Tickets 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, with the account that holds your productions. If a colleague or a venue partner owns them, ask for read or write access first.

  3. 03

    Grant access

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

First Zap

Your first Zap: email each new ticket's wallet link

GoalWhen a ticket is issued for your production, the Zap fetches the link to its wallet pass and sends it by email.

  1. 01

    Build: pick the trigger

    Create a Zap, choose PassKit Event Tickets and New Ticket Issued. Select your connection, then the production to watch: the trigger needs its Production Id.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent tickets of that production. Pick one so the next steps are mapped on a real ticket, not on empty sample data.

  3. 03

    Get the pass link

    Add Get Event Ticket Pass URL, choose the Format of the link, and map one identifier from the trigger: ticket ID, ticket number or order number. This second action makes the Zap multi-step: paid plan.

  4. 04

    Add the email

    Add an email step, map the recipient from the test ticket if it carries an address, and paste the pass link into the message. Test each step once and read the result.

  5. 05

    Publish

    Click Publish. From then on, every ticket issued for that production sends its link. Tickets issued earlier stay out, so handle those separately.

Triggers

The 3 PassKit Event Tickets triggers

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

1

Ticket Installed

Instant trigger

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

Starts the Zap when a guest adds one of your tickets to the wallet on their phone. It tells you the ticket did not just leave your system: the guest kept it, which is the signal to prepare for the people who are really coming.

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 conference team wants a sheet of who has saved their badge, to chase the others before the day.
Watch out
PassKit only learns about the install once the guest's phone is online, so an offline phone reports it later.
2

New Ticket Issued

Instant trigger

In Zapier“Triggers when a new ticket is issued for a Production.”

Reacts each time a new ticket is created for a production, whoever issued it: your team in PassKit, another Zap or another tool. It is the natural place to send the ticket on, log the sale or alert the box office.

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 concert promoter wants every new ticket copied to the CRM record of the buyer.
Watch out
the trigger asks for a Production Id, so one Zap watches one production; a second show needs its own Zap.
3

Ticket Updated

Instant trigger

In Zapier“Triggers when a ticket is updated in a Production.”

Fires when a ticket of a given production changes. Your other tools follow the ticket instead of keeping the version from the day it was sold, which matters when a holder corrects their details.

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 festival keeps a guest list in a spreadsheet and wants each change reflected there.
Watch out
a Zap that edits tickets of the same production, with Patch Person for instance, may wake this trigger again; check it in a test before publishing.
Actions

The 10 PassKit Event Tickets actions

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

1

Get Event Ticket Pass URL

Action

In Zapier“Retrieves digital event ticket pass(es) in the requested format based on the index provided. Only one of ticketId, ticketNumber or orderNumber is required.”

Returns the link to a ticket's wallet pass, or to several passes, in the format you choose. One identifier is enough: ticket ID, ticket number or order number.

When to use it
you send tickets from your own email tool rather than from PassKit.
Watch out
the Format field is required; leave it empty and no link comes back.
2

Get Ticket by Id

Action

In Zapier“Gets a Ticket record by ID.”

Fetches a full ticket 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

Get Ticket by Ticket Number

Action

In Zapier“Gets a Ticket record by Ticket Number.”

Fetches a ticket from its ticket number within a given production.

When to use it
the number printed on the ticket is all your support team has when a guest writes in.
Watch out
it is an action, not a search step, so each successful lookup costs a task.
4

Get Ticket by Order Number

Action

In Zapier“Gets a Ticket record by Order Number.”

Starts from the order number a ticket was sold under and returns that ticket, within a given production.

When to use it
your shop knows the order, not the ticket, and the Zap needs the ticket behind it.
Watch out
without the Production Id the lookup cannot run, even with a valid order number.
5

Issue Ticket by Date

Action

In Zapier“Issue a new ticket for the provided date.”

Builds a ticket from scratch for the date you give, inside a production and at a venue, with its start and end date and time.

When to use it
you sell sessions booked in another tool and each booking carries its own date.
Watch out
five fields are required here, production, venue, ticket design, start and end; a missing one makes the step fail.
6

Issue Ticket by Event Id

Action

In Zapier“Issue a new ticket for an exiting event.”

Creates a new ticket for an event that already exists in PassKit, using the ticket design you pick.

When to use it
a paid order or a registration in another tool should hand the guest a ticket for a known date.
Watch out
it needs the Event Id and the Ticket Type Id, so the event and its design must be ready first.
7

Patch Person

Action

In Zapier“Updates personal information of a ticket holder”

Edits the personal information of a ticket holder and leaves the ticket itself alone.

When to use it
a guest corrects their details in your registration tool and the ticket in their wallet should follow.
Watch out
if a Zap of yours listens to Ticket Updated on that production, test whether this change sets it off.
8

Redeem Ticket

Action

In Zapier“Redeems a ticket by either internal PassKit ID or Ticket Number.”

Marks one ticket as used, found by its PassKit ID or by its ticket number.

When to use it
your check-in tool scans a guest at the door and PassKit should know the ticket was spent.
Watch out
pick the identifier your scanning tool really holds; mapping one where the other is expected means the ticket is not found.
9

Redeem Ticket by Order Number

Action

In Zapier“Redeems existing Tickets by Order Number. Use this endpoint when you want to capture redemption data and trigger the switch to the redeemed design of the Ticket.”

Redeems the tickets of an order in one go, records the redemption and switches them to their redeemed design.

When to use it
a group arrives together and the whole order is checked in at once.
Watch out
it needs the Production Id with the Order Number, and it acts on every ticket of that order.
10

Validate Ticket

Action

In Zapier“Validates an existing Ticket. Use this endpoint when you want to check validity of a ticket. Tickets can be validated multiple times. Requires ticket.id to be set, or ticket.ticketNumber + ticket.event.production.id to be set.”

Checks that a ticket is valid, as many times as needed, from its ID or from its ticket number plus production.

When to use it
a pass covering several entries is scanned at each one and must stay usable until the last.
Watch out
the required Maximum Number of Validations redeems the ticket automatically once that number is reached.
When it breaks

When a PassKit Event Tickets Zap breaks

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

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

  • Tickets sold before the Zap are ignored

    A Zap only reacts to what happens after you publish it. Tickets issued, updated or installed before are never picked up; sending those passes is a separate job.

  • A Zap that sets itself off

    A Zap that changes tickets of the production its own Ticket Updated trigger watches can restart on every run, and burns through the task count fast.

  • A bulk issue is held back

    Issuing a huge batch of tickets 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

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

  • A pass redeemed by its own validations

    Validate Ticket redeems the ticket once the Maximum Number of Validations is reached. Set it too low on a multi-entry pass and the ticket is redeemed before its last entry.

  • One production per Zap

    Each trigger and several actions require a Production Id. A Zap set on one production ignores the others, so a new show needs its own Zap or a changed setting.
Need help

Need help automating PassKit Event Tickets with Zapier?

A person reads every message.

FAQ

PassKit Event Tickets Zapier integration: frequent questions

01Is the PassKit Event Tickets Zapier integration free?
Yes, for simple Zaps. PassKit Event Tickets 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, one trigger and one action. New Ticket Issued followed by Get Event Ticket Pass URL fits. Add an email to send that link and you have three steps, which needs a paid plan. A filter counts as a step too, so it has the same effect.
02How many tasks does a PassKit Event Tickets Zap use?
One task for each action that completes, nothing for the trigger. A Zap that issues a ticket for each paid order spends one task per order. Add Get Event Ticket Pass URL and an email, and each order costs three. The four Get actions are billed like any other action, since this app has no search steps. A failed action is not counted. Waiting for new tickets costs nothing, however many your productions sell.
03Are PassKit Event Tickets 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 Ticket Installed: PassKit itself only knows about the install once the guest's phone is online, so a delay can come from the phone, not from Zapier.
04What do you need to connect a PassKit Event Tickets account?
A PassKit account that holds your productions, plus read or write access to any you do not own. In Zapier, open the Apps page, click + Add connection, choose PassKit Event Tickets, sign in in the tab that opens and approve the access. Then prepare the IDs: every trigger asks for a Production Id, issuing by date needs a Venue Id and a Ticket Type Id, and issuing by event needs an Event Id.
05Why is a multi-entry pass redeemed too early?
Most likely because of Validate Ticket. That action can check a ticket several times, but it asks for a Maximum Number of Validations, and once that number is reached it redeems the ticket automatically. If the number is lower than the scans the pass will really get, the ticket is redeemed before its last entries. Set it to the number of entries the ticket is meant to allow, and keep Redeem Ticket for single-entry passes.
06What if the PassKit Event Tickets operation you need is missing on Zapier?
Then the Zap cannot do it directly. The integration covers 3 triggers and 10 actions: issue, validate, redeem, fetch tickets and pass links, and patch holder details. There is no trigger on a redemption, no action to cancel a ticket, no search step, and nothing to create productions or venues. Rework the scenario around what exists, or prepare those parts in PassKit by hand. The app page on Zapier lists the operations currently offered in the editor.
07Zapier, Make or n8n for PassKit Event Tickets?
Choose by the shape of the job, not by a ranking. On Zapier, PassKit Event Tickets offers 3 instant triggers and 10 actions, works on the free plan and connects with a sign-in. The trade-offs are clear: two steps on the free plan, and every completed action billed, lookups included. If each Zap does one thing, like issuing a ticket after an order, that fits well. If every run chains a lookup, a pass link and an email, 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