Resources · Zapier integration

Passage Ticketing Zapier integrationAutomate Passage Ticketing with Zapier.

The Passage Ticketing Zapier integration gives you 3 triggers, 0 actions and 0 searches. Every ticket order, merchandise sale and redemption in Passage can start work in your other tools, the moment it happens, even on the free plan.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Passage Ticketing Zapier integration does

Passage is a ticketing platform for event organisers: it sells tickets, merchandise and concessions, online and at the door. With Zapier, Passage becomes a source of signals. A sale or a redemption in Passage starts an automation in the tools you already use for accounting, marketing or reporting.

Three results come out of it. First, a live sales log: New Transaction sends each order for an event to a spreadsheet or an accounting tool, without exports at the end of the night. Second, a clear view of side income: Product Sale follows one product, a T-shirt or a drink voucher, and can feed your stock sheet or alert the person running the stand. Third, a record of who actually came: Redemption Feed reports each item redeemed for an event, which is the raw material for a thank-you email or an attendance report in your CRM.

Now what Zapier does not do for Passage. There are no actions and no searches. Zapier cannot create an event, issue a ticket, refund an order or change anything inside Passage. The flow only goes one way: out of Passage, into your other tools.

On the bright side, all three triggers are instant, so even the free plan gets them without waiting.

If you are weighing other platforms, the comparisons sit here: n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the rest of this page. Each gets a plain definition here, then the page uses it without explaining it again.

Zap
The automation you build on Zapier: one trigger, followed by one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a ticket order in Passage. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, in another app here.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Connection
Your Passage account linked to Zapier once, then reused by every Zap that starts from Passage Ticketing.
Cost

What a Passage Ticketing Zap really costs

Passage Ticketing is not one of the apps Zapier keeps for paid plans: it works on the free plan. And since it only offers triggers, Passage itself never costs you a task.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan stepsOne trigger and one action, nothing more
  • Passage triggers3 instant, so no waiting on any plan
  • BilledEach successful action, never the trigger

Only a successful action costs a task, and here every action belongs to another app. The trigger never costs anything, and an action that fails is not counted. Each successful action counts on its own: a Zap that logs a sale and then posts a message uses two tasks per order. The free plan stops at two steps, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below concerns polling triggers only: the three Passage triggers are instant, so they fire straight away on every plan.

Connect

Connect your Passage Ticketing account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to the Apps page and click + Add connection. You need a Passage account, plus access to any event or product you did not create yourself and want the Zap to watch.

  2. 02

    Pick Passage Ticketing

    Type Passage into the search box of the dialog, select Passage Ticketing, then confirm with Add connection. A new tab opens on the Passage side so you can show the account is yours.

  3. 03

    Sign in and grant access

    Sign in to Passage in that tab and allow Zapier to use the account. The connection then appears on the Apps page, and each Zap picks it from a list instead of asking you again.

First Zap

Your first Passage Ticketing Zap, step by step

GoalEach paid order for your event lands as a row in a sales sheet, with complimentary tickets left out.

  1. 01

    Pick the trigger

    Create a Zap, choose Passage Ticketing, then New Transaction. Pick the event in the Event field, and set Include Comps to no if free tickets should stay out of the sheet.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real order rather than an empty template.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field, the rule and the value. Use a number rule on amounts and a text rule on text, or the filter never lets anything through.

  4. 04

    Add the spreadsheet step

    Add the app that receives the data, here a spreadsheet, and map the order details from the trigger into its columns. That step is the only one that costs a task.

  5. 05

    Test, then publish

    Test each step and read what came back. Then click Publish to switch the Zap on. With the filter it is a multi-step Zap, so it runs on a paid plan.

Triggers

The 3 Passage Ticketing triggers

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

1

Product Sale

Instant trigger

In Zapier“Triggers when a product is sold”

Fires each time a given product sells in Passage. It follows the product you pick, whether it is merchandise, a concession item or another add-on, rather than the whole order.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the person running the merch stand wants a message in the team chat for each hoodie sold, to restock before the table empties.
Watch out
the Product field is mandatory, so one Zap follows the product you chose there, not every product of the event.
2

Redemption Feed

Instant trigger

In Zapier“Triggers when an item is redeemed”

Reports each item redeemed for an event. It is the signal that a ticket or an item has actually been used, not just bought.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want to mark attendees as present in your CRM, so the thank-you email after the show only goes to people who came.
Watch out
the Event field is mandatory, so the Zap watches the event you selected there and stays silent about any other one.
3

New Transaction

Instant trigger

In Zapier“Triggers when a new transaction is created.”

Starts the Zap whenever a new transaction is created for an event. It is the broadest of the three, the one to use for anything built on sales.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your treasurer wants every order in the accounting sheet as it happens, instead of an export after the event.
Watch out
Include Comps is mandatory and decides whether complimentary tickets also start the Zap; leave it on yes and guest lists end up in your revenue.
When it breaks

When a Passage Ticketing Zap breaks

Zapier attaches no help article to Passage Ticketing, and no limit specific to the app has been recorded. What breaks is the general Zapier behaviour plus the two settings every Passage trigger asks for.

Four cases are worth knowing before you switch the Zap on. When one of them shows up, start with the Zapier troubleshooting page.

  • Early ticket sales never show up

    A Zap only reacts to what happens after it is switched on. Orders taken before that stay out of your sheet until you move that backlog separately.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold that batch back.

  • Comp tickets inflate the numbers

    New Transaction counts complimentary tickets too when Include Comps is on. Revenue reports then mix paid orders with guest lists.

  • The wrong event is watched

    Redemption Feed and New Transaction follow the Event chosen in the trigger. A Zap set on last season's event stays quiet for the new one.
Need help

Need help automating Passage Ticketing with Zapier?

A person reads every message.

FAQ

Passage Ticketing Zapier integration: frequent questions

01Is the Passage Ticketing Zapier integration free?
Yes on the Zapier side: Passage Ticketing works on the free plan, because Zapier does not keep it for paid plans. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. That covers New Transaction feeding a spreadsheet. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Your Passage subscription and fees are a separate matter, not covered on this page.
02How many tasks does a Passage Ticketing Zap use?
Passage itself uses none, because it only offers triggers and a trigger never costs a task. What counts is each successful action in the other apps. A Zap that logs every order in a spreadsheet uses one task per order. If it also posts a message in your team chat, that is two per order, since each successful action counts on its own. An action that fails is not counted. On a busy on-sale day, the number of orders is what drives your task count.
03Does Passage Ticketing work in real time with Zapier?
Yes, all three Passage triggers are instant. Passage reports Product Sale, Redemption Feed and New Transaction to Zapier the moment they happen, so the Zap starts right away, whatever the plan. The polling grid of 15 minutes on Free, 2 on Professional and one on Team and Enterprise does not apply to them. The editor shows a lightning bolt on Zaps built on an instant trigger, so you can check it before you publish.
04What does it take to connect Passage Ticketing to Zapier?
A Passage account, and access to any event or product you did not create yourself but want a Zap to watch. The connection takes three moves: open the Apps page of Zapier and click + Add connection, search for Passage Ticketing and confirm with Add connection, then sign in to Passage in the tab that opens and grant access. Every Zap then reuses that connection from a list, and each trigger asks for the event or product to follow.
05Why do complimentary tickets show up in a Passage sales Zap?
Because New Transaction has a mandatory Include Comps setting, and set to yes it starts the Zap for comp tickets as well. Free guest-list tickets then appear next to paid orders in whatever the Zap feeds. Set Include Comps to no when the Zap is about revenue, and keep it on yes when it is about headcount. If you need both views, build two Zaps on the same event, one with each setting, and keep in mind each one uses its own tasks.
06What if the Passage Ticketing operation you want is not in Zapier?
Then it is not available through Zapier today. The editor offers three triggers for Passage Ticketing and nothing else: no action and no search. That rules out creating events, issuing tickets or changing an order from a Zap. The workable pattern is to let Passage start the Zap and do the work in the next app, a spreadsheet, a CRM or an email tool. Anything that has to change inside Passage stays in the Passage interface.
07Zapier, Make or n8n for Passage Ticketing?
Choose on criteria rather than reputation. On Zapier, Passage Ticketing brings three instant triggers, no action and no search, and works on the free plan for two-step Zaps. So check three things: whether you only need to push Passage data out, or also to write into Passage; whether your flows need several steps, which means a paid plan here; and whether the other platform offers the same three triggers as instant ones. Then compare on those points.
Same platform

Other docs you might need on this stack.

Browse all integrations