Resources · Zapier integration

Ticket Tailor Zapier integrationAutomate Ticket Tailor with Zapier.

The Ticket Tailor Zapier integration gives you 10 triggers and 74 actions, and no search step. All ten triggers are instant, so orders, tickets and memberships reach your Zap right away, even on the free plan. Here is what each one does, and where it bites.

See the 84 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Ticket Tailor Zapier integration actually does for your box office

The Ticket Tailor Zapier integration links your box office to Zapier, the tool that runs automations between apps. Something happens in Ticket Tailor (an order, a ticket, a waitlist signup) and Zapier carries out the next step for you, in Ticket Tailor itself or in another tool you use.

Three results come up again and again. First, a box office that reacts on its own: Order Created fires the second someone buys, and Create Voucher or Create Discount can reward that buyer without anyone opening the dashboard. Second, a programme you manage from outside: Create Event Series, Create Event Occurrence and Create Ticket Type build a whole run of dates from a planning sheet or a form. Third, memberships that look after themselves: Issued Membership Created reports each new member the moment the membership is issued, and Create Issued Membership Redemption records each visit when your door system logs one.

Now the limits. There is no search step for this app, so the Zap cannot look up an order by an attendee's email; the read actions want an identifier such as or_ or ev_, or return a whole list. Void Issued Ticket marks a ticket as no longer valid, but it does not refund anyone or cancel the order. And Create Issued Ticket (Fees Apply) carries a fee per issued ticket, even for free tickets.

If you are still weighing tools, the Ticket Tailor Make integration covers the same app on Make, and n8n vs Zapier sets the two side by side, criterion by criterion.

Vocabulary

Zapier words you will meet on this page

Eight words, in plain English. Each one comes back further down without a second explanation.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it to happen.
Action
What the Zap does once it has started: the step that creates, updates, sends or reads something on your behalf.
Task
The unit Zapier bills you for: one action your Zap finishes successfully. The number on your plan counts those.
Instant trigger
A trigger the app reports itself: Ticket Tailor calls Zapier as soon as the event happens, so nothing waits for a timer.
Polling trigger
The other kind: Zapier asks the app for new items at a fixed interval set by your plan. None of the Ticket Tailor triggers work this way.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your Ticket Tailor account linked to Zapier once, then reused by every step of every Zap that touches Ticket Tailor.
Cost

What a Ticket Tailor Zap really costs you

Zapier counts tasks, not Zaps. With Ticket Tailor that works in your favour on the trigger side.

  • Premium appNo, it works on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger typeAll 10 triggers are instant
  • BilledEach successful action, one task each

The trigger never costs a task, and neither does Zapier waiting for new orders. Every action that succeeds counts once, so a Zap with three actions burns three tasks per order. An action that fails is not billed. The free plan gives you 100 tasks a month and an unlimited number of Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter or a second action and it becomes a multi-step Zap, which needs a paid plan. The interval grid below only matters for polling triggers, and Ticket Tailor has none.

Connect

Connect your Ticket Tailor account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an existing Ticket Tailor account, plus read or write access to anything you do not own that the Zap should touch.

  2. 02

    Pick Ticket Tailor

    Type Ticket Tailor in the search box of the dialog that opens, select it in the results, then click Add connection. A new tab opens on the Ticket Tailor side for the next step.

  3. 03

    Sign in and allow access

    Log in to Ticket Tailor in that tab and grant Zapier access to the account. From then on, every Zap step that uses Ticket Tailor can reuse this single connection.

First Zap

Your first Zap: reward your best buyers with a voucher

GoalA workshop organiser creates a thank-you voucher for every order that passes a value they choose.

  1. 01

    Build: set the trigger

    Create a Zap, choose Ticket Tailor as the app and Order Created as the event, then select your connection. This is the step that starts everything.

  2. 02

    Test the trigger

    Click test. Zapier brings back the three most recent orders of your account, so you map the next steps on a real one. Amounts arrive in cents, with no decimals.

  3. 03

    Add the filter

    Add a Filter step from the plus icon, pick the order amount, a number rule and your threshold in cents. A text rule here would never pass.

  4. 04

    Add Create Voucher

    Add the action Create Voucher, give it a name and a value. The value is in cents too, so a voucher worth ten units of your currency takes a value a hundred times larger.

  5. 05

    Test and publish

    Run the action once and check the new voucher in Ticket Tailor, then click Publish. With a filter this Zap has three steps, so it needs a paid plan.

Triggers

The 10 Ticket Tailor triggers

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

1

Event Created

Instant trigger

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

Starts your Zap whenever a brand new event appears in your box office. The Zap receives that event and can pass it to any later step.

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 theatre company that wants every new show announced to its front-of-house team without someone copying details across.
Watch out
events created before the Zap was published never come through, so only new ones start it.
2

Event Deleted

Instant trigger

In Zapier“Triggers when an existing event is deleted.”

Fires when an event you already had is removed from Ticket Tailor. It is the only way for another tool to learn that a date is gone, since nothing else in this integration reports a removal.

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 venue manager who needs a cancelled date pulled from the staff rota the moment the event disappears.
Watch out
deletions made before the Zap was published are never picked up, so clean up older gaps by hand.
3

Event Updated

Instant trigger

In Zapier“Triggers when an existing event is updated.”

Reacts each time an existing event is updated in Ticket Tailor. Every update starts a run of its own, so a busy afternoon of edits means many runs.

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 tour promoter keeping a partner listing in step whenever a date or venue moves.
Watch out
pairing it with Update Event Occurrence on the same event writes into what the trigger watches and sets the Zap off again and again.
4

Issued Membership Created

Instant trigger

In Zapier“Triggers when a new issued membership is created.”

Runs each time a new membership is issued in your box office. That gives you a clean starting point for any onboarding sequence.

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 film club that sends each new member a welcome pack and adds them to its member list on day one.
Watch out
memberships issued before the Zap was published will never come through, so welcome existing members another way.
5

Issued Membership Updated

Instant trigger

In Zapier“Triggers when existing issued membership is updated”

Picks up changes to a membership a member already holds. Your Zap gets the updated membership to act on.

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 gallery whose patrons scheme keeps a separate contact list, and wants it corrected whenever a membership record changes.
Watch out
Void Issued Membership and Update Issued Membership both change a membership, so using either in the same Zap can make it trigger itself.
6

Issued Ticket Created

Instant trigger

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

Goes off for every single ticket issued, not for every order. A group order of four seats therefore means four runs. Each action behind the trigger is billed four times as well.

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 host who needs one badge line per attendee rather than one per buyer.
Watch out
on a big on-sale this trigger multiplies fast, so count your monthly tasks before you switch it on.
7

Issued Ticket Updated

Instant trigger

In Zapier“Triggers when an existing issued ticket is updated.”

Notices when a ticket that already exists changes in your box office. The Zap receives the ticket as it now stands and can hand it to the next step.

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 team that keeps a live attendee sheet in another tool and wants each ticket change reflected there.
Watch out
Void Issued Ticket changes a ticket, so a Zap that uses it after this trigger risks running in circles.
8

Order Created

Instant trigger

In Zapier“Triggers when new order is created (currency values are always in cents, or equivalent, with no decimals).”

The trigger most box offices start with: a new order lands and the Zap runs once for that order, whatever the number of tickets inside it. Every amount it carries is in cents, with no decimals.

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 cooking school that creates a thank-you voucher straight after each checkout.
Watch out
a filter on the order value needs its threshold written in cents too, otherwise almost every order passes.
9

Order Updated

Instant trigger

In Zapier“Triggers when existing order is updated (currency values are always in cents, or equivalent, with no decimals).”

Starts the Zap whenever an order that already exists changes. Amounts again come in cents, without decimals.

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 charity gala that takes bank transfers and wants the accounts team told the moment an order moves on.
Watch out
following it with Update Order on the same order makes the Zap retrigger itself.
10

Waitlist Signup Created

Instant trigger

In Zapier“Triggers when a new waitlist signup is created.”

Fires when someone joins the waitlist of an event series. You point the trigger at one event series, and only signups on that series start the Zap.

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 comedy club that wants to know quickly how many fans are queuing for a sold-out run.
Watch out
the event series ID, starting with es_, is mandatory, so each series you follow needs its own Zap.
Actions

The 74 Ticket Tailor actions, grouped by what they do

Ticket Tailor gives you 74 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Box Office Overview

Action

In Zapier“Show box office statistics information.”

Pulls statistics on your box office as a whole and hands them to the next step. It needs no ID at all.

When to use it
a promoter sending headline sales figures to the team channel whenever a new date is created.
Watch out
on the free plan this action has to be the only one in the Zap.
2

Create Bundle

Action

In Zapier“Create a bundle for the given event series ID.”

Packages several ticket types of one series into a single offer with its own price. It needs the series ID, a name, a description, a price in cents and the ticket type IDs to include.

When to use it
a music venue creating a weekend pass once both nights of a series are on sale.
3

Delete Bundle

Action

In Zapier“Delete a bundle. This action is irreversible. The bundle will be permanently removed.”

Removes a bundle from a series permanently. It requires the series ID and the bu_ code. Ticket Tailor flags it as irreversible: the bundle is removed for good.

When to use it
a music venue withdrawing a weekend pass once one of its two nights is cancelled in the programming calendar.
4

Update Bundle

Action

In Zapier“Update existing bundle.”

Modifies an existing bundle. Give it the series ID and the bundle code starting with bu_. Both codes are mandatory; Get List of Event Series gives you the es_ one.

When to use it
a venue refreshing the description of its weekend pass whenever the line-up changes in the programming sheet.
5

Create Check-In (Out)

Action

In Zapier“Create check-in or check-out.”

Records an attendee coming in or going out, on one issued ticket. Quantity 1 checks in, -1 checks out, and the ticket ID starts with it_.

When to use it
a summit using a separate badge scanner that should mark arrivals in Ticket Tailor too.
6

Get List of Check-Ins

Action

In Zapier“Returns a list of check-ins.”

Returns the check-ins recorded so far, with no ID to supply. It gives another tool the arrival picture that Ticket Tailor already holds.

When to use it
a festival safety officer who wants entry figures copied into an incident log each time an event is updated.
7

Create Discount

Action

In Zapier“Creates a discount code that can be used on checkout.”

Generates a discount code buyers can type at checkout. You give it a descriptive name, the code itself and a type: a fixed amount or a percentage.

When to use it
a sports club creating a code for each partner company as soon as the deal is signed in its CRM.
8

Delete Discount

Action

In Zapier“Delete a discount. This action is irreversible. The discount will be permanently removed.”

Permanently removes a discount code, found through its di_ identifier. Buyers who try the code afterwards will find it no longer works.

When to use it
a sports club killing a partner code the moment the partnership is marked as ended in its CRM.
9

Get Discount

Action

In Zapier“Returns a single discount; all currency values are in cents (or equivalent), with no decimals.”

Fetches one discount from its di_ code, with currency values in cents. Later steps can then compare what is set up with what was agreed.

When to use it
a partnership manager confirming a partner's code is still configured the way the contract in the CRM says.
10

Get List of Discounts

Action

In Zapier“Returns a list of discounts.”

Returns every discount code of the box office, no ID needed. Use it as a snapshot of what promotions are currently configured.

When to use it
a marketing lead auditing which promo codes are live before launching a new campaign, so two codes never compete for the same buyers.
11

Update Discount

Action

In Zapier“Updates an existing discount.”

Edits a discount code that already exists, using its identifier beginning with di_. Handy for extending or tweaking a code without recreating it.

When to use it
a sports club updating a partner code when the partnership terms change in its CRM.
12

Get Event

Action

In Zapier“Returns a single event; all currency values are in cents (or equivalent), with no decimals.”

Fetches one event from its ev_ code so later steps can use its details. Amounts come back in cents.

When to use it
a festival that needs an event's full details after an order, to write a personalised message to the buyer.
13

Get List of Events

Action

In Zapier“Returns a list of events.”

Returns your events as a list, without needing an ID. It replaces the search step this app does not have, at the cost of handling a list.

When to use it
a venue pushing its full calendar to a display screen tool.
14

Create Event Occurrence

Action

In Zapier“Create event for event series.”

Adds one dated event to a series you already have. You give it the series ID, a start date and an end date written as YYYY-MM-dd.

When to use it
a yoga studio that adds next month's sessions to its series from a timetable kept elsewhere.
Watch out
write both dates exactly in that format, since it is the one the fields ask for.
15

Delete Event Occurrence

Action

In Zapier“Delete event occurrence.”

Removes one date from a series, using both the series ID and the occurrence ID. The series code starts with es_ and the occurrence code with ev_; Get List of Event Occurrences gives you both.

When to use it
a yoga studio dropping a session the teacher cancelled in the staff calendar.
16

Get Event Occurrence

Action

In Zapier“Returns a single event occurrence; all currency values are in cents (or equivalent), with no decimals.”

Reads one date of a series. You provide the series ID and the occurrence ID, and amounts return in cents, ready to be mapped into the next step.

When to use it
a touring company pulling a date's details to brief the local crew as soon as an order comes in for it.
17

Get List of Event Occurrences

Action

In Zapier“Returns a list of event occurrences.”

Returns every date that belongs to one series, from the series code beginning with es_. The result is a list, which the next step has to be able to handle.

When to use it
a dance school publishing its full term schedule to the parents' newsletter tool whenever the series changes.
18

Update Event Occurrence

Action

In Zapier“Updates an existing event occurrence.”

Changes one dated event inside a series. Both the series ID (es_) and the occurrence ID (ev_) are required.

When to use it
a touring show correcting a single date after a venue moves the start time in the shared booking calendar.
19

Event Series Change Status

Action

In Zapier“Change status for a given event series.”

Switches a series to a new status without editing anything else. You give the series ID and the target status. Both fields are mandatory, and Get List of Event Series hands you the series code if it is not to hand.

When to use it
a summer camp that publishes its series only once the venue contract is marked signed.
20

Create Event Series

Action

In Zapier“Creates a new event series.”

Opens a new event series in your box office, the container that later holds dates, ticket types and bundles. Only a name is required to get started.

When to use it
a training company that turns each new course approved in its planning tool into a series ready for dates.
21

Delete Event Series

Action

In Zapier“Deletes event series.”

Removes a whole event series from its es_ code. Think twice: this is the widest delete in the app, because a series is the container of dates, ticket types and bundles.

When to use it
a training company clearing a course that was cancelled before any date was published.
22

Get Event Series

Action

In Zapier“Returns a single event series; all currency values are in cents (or equivalent), with no decimals.”

Reads a single event series from its es_ code and passes its details to the steps that follow, with currency amounts in cents.

When to use it
a conference that wants the series name in each order confirmation it sends from another app, rather than the bare event details carried by the order.
23

Get List of Event Series

Action

In Zapier“Returns a list of event series.”

Lists all your event series in one go, with no ID required. It is also the easiest way to find the es_ code that so many other actions ask for.

When to use it
a training provider syncing its course catalogue into a planning tool each time a new event is created.
24

Get List of Event Series Overrides

Action

In Zapier“Returns a list of event series overrides.”

Brings back every override set on one event series, from its es_ code, so a later step can check which exceptions apply before acting.

When to use it
a theatre checking which exceptions are active on a run before a Zap changes prices with Update Ticket Type.
25

Update Event Series

Action

In Zapier“Updates an existing event series.”

Edits an event series you already have, identified by its es_ code.

When to use it
a lecture programme renaming a series after the speaker list is finalised in another tool.
Watch out
paired with Event Updated it can trigger itself.
26

Create Hold

Action

In Zapier“Creates a new hold in the system.”

Reserves seats of one ticket type on one event so they leave general sale. It requires the event ID, the ticket type ID and a note explaining the hold.

When to use it
a concert promoter setting aside guest-list seats for each new date added to the tour.
27

Delete Hold

Action

In Zapier“Delete a hold. This action is irreversible. The hold will be permanently removed.”

Releases a hold for good, from its ho_ code, which takes the reservation away from the seats it covered.

When to use it
a promoter freeing unused guest-list seats once guests have confirmed through a form.
Watch out
the hold cannot be restored afterwards, so a mistaken run means setting it up again.
28

Get Hold

Action

In Zapier“Returns a single hold.”

Reads one hold from its code starting with ho_, so you can see what is reserved and the note that explains why it was set aside.

When to use it
a box office manager reviewing a guest-list hold before deciding to release it with Delete Hold.
29

Get List of Holds

Action

In Zapier“Returns a list of holds.”

Collects every hold of the box office in one go, no ID needed. It is the quickest view of seats kept off general sale across all events.

When to use it
a promoter checking which seats are still set aside when a show is updated, before releasing them to the public.
30

Create Issued Membership

Action

In Zapier“Creates a new issued membership.”

Gives a membership of an existing type to one person. It needs the membership type ID, plus the member's first name, last name and email.

When to use it
a coworking space that grants event access to every new tenant signed in its billing tool.
31

Create Issued Membership Redemption

Action

In Zapier“Creates a redemption for an issued membership at a specific event. This records that the issued membership was used for entry to the event.”

Logs that a member used their membership to enter a specific event. It asks for the event ID and the membership code being redeemed.

When to use it
a members' cinema that counts visits per member to spot its most loyal regulars.
32

Get Issued Membership

Action

In Zapier“Returns a single issued membership.”

Opens the record of one membership a member holds, from its ID such as im_123, and hands it to the steps after it.

When to use it
a members' bar checking a membership before applying a perk in its till software, so staff never apply a discount to an expired pass.
33

Get Issued Membership Photo

Action

In Zapier“Returns a temporary signed URL for the issued membership photo.”

Returns a temporary signed link to a member's photo, from the membership code.

When to use it
a climbing gym that shows the photo on its front-desk screen when a member arrives.
Watch out
the link is temporary, so use it straight away rather than storing it.
34

Get List of Issued Memberships

Action

In Zapier“Returns a list of issued memberships.”

Brings back all the memberships you have issued, no ID required. It is a list, not a single member, so plan a step that can deal with several items.

When to use it
a cultural centre refreshing its member mailing list from Ticket Tailor whenever a membership type changes.
35

Update Issued Membership

Action

In Zapier“Updates an existing issued membership.”

Corrects a membership a person already holds, located by its ID such as im_123.

When to use it
an arts centre fixing a member's details once they update them in the CRM.
Watch out
with Issued Membership Updated as the trigger, this action can loop.
36

Void Issued Membership

Action

In Zapier“Voids an existing issued membership.”

Cancels the validity of a membership a person holds, located by its ID such as im_123. From then on the membership no longer counts as valid.

When to use it
a club ending access for a member whose subscription was stopped in its billing tool.
37

Create Issued Ticket (Fees Apply)

Action

In Zapier“Creates a new issued ticket for an event occurrence from the available inventory. This action incurs a fee per issued ticket, even if the ticket is free. Send the event_id and ticket_type_id to create the issued ticket from an event occurrence's ticket type allocation. Alternatively, send the hold_id to create the issued ticket from a pre-existing hold. The issued ticket is not associated to an order. The request will fail if no tickets are available to fulfil the request, or the ticket type is a 'seated' type (uses a seating chart).”

Issues a ticket outside any order, either from a ticket type's allocation or from an existing hold. The attendee's full name is mandatory.

When to use it
a trade show sending complimentary tickets to speakers confirmed elsewhere.
Watch out
Ticket Tailor charges a fee per ticket even when it is free, and seated ticket types are refused.
38

Get Issued Ticket

Action

In Zapier“Returns a single issued ticket.”

Looks up one issued ticket from its it_ code, so the next step can use what Ticket Tailor holds about it. You need the code; there is no lookup by attendee name.

When to use it
an access-control team checking a ticket before printing a wristband at a separate desk.
39

Get List of Issued Tickets

Action

In Zapier“Returns a list of issued tickets.”

Pulls the issued tickets of your box office as a list, without asking for an ID. Handy when a later step needs the whole attendee base rather than one ticket.

When to use it
a conference exporting attendees to a badge printing service when its registration desk opens.
40

Void Issued Ticket

Action

In Zapier“Mark an issued ticket as voided. This action is irreversible. This will only mark the ticket as voided (no longer valid) and will not cancel an entire order or issue a refund. You can also void an issued ticket to a hold, which will create a hold from the issued ticket and not put the allocation back on sale.”

Marks one issued ticket as no longer valid, from its it_ code. You can also void it into a hold, keeping the seat off sale.

When to use it
a venue cancelling a duplicate ticket flagged by its door team.
Watch out
this cannot be undone, and it neither refunds nor cancels the order.
41

Create Membership Type

Action

In Zapier“Creates a new membership type.”

Defines a new kind of membership, with a name and the rules for when it starts and ends, either fixed dates or relative to the day it is issued. You can also require a photo.

When to use it
a museum launching a seasonal pass designed in a planning doc.
42

Delete Membership Type

Action

In Zapier“Delete membership type.”

Removes a membership type, located by its ID such as mt_123. Plan where new members should go before retiring it.

When to use it
a museum retiring a seasonal pass once the season is over, after checking with Get List of Issued Memberships who still holds it.
43

Get Membership Type

Action

In Zapier“Returns a single membership type.”

Fetches the settings of one membership type, from its code beginning with mt_, including its name and how its validity is worked out.

When to use it
a museum adding the pass name and validity rules to a welcome message sent from another tool after each new membership.
44

Get List of Membership Types

Action

In Zapier“Returns a list of membership types.”

Gives you every membership type you have defined, so you can find the mt_ code that Create Issued Membership asks for.

When to use it
a club checking which passes exist before granting one from its sign-up form, so the form never points at a type that was removed.
45

Update Membership Type

Action

In Zapier“Updates an existing membership type.”

Edits a membership type, for instance to start or stop requiring a photo. It finds the type through its ID, written like mt_123.

When to use it
a gym tightening the rules of its annual pass after a policy change.
46

Confirm an Offline Payment Has Been Paid

Action

In Zapier“Confirm that an offline payment has been paid.”

Marks an order paid offline as settled, from its or_ code. That spares someone a manual click per transfer.

When to use it
a charity ball that matches bank transfers in its accounting tool and wants orders confirmed as soon as the money is matched.
47

Get Order

Action

In Zapier“Returns an order belonging to the box office; all currency values are in cents (or equivalent), with no decimals.”

Retrieves one order of the box office from its or_ code, with amounts in cents, so the following steps can use the full order rather than what the trigger carried.

When to use it
a support desk that needs the whole order when a buyer writes in quoting their reference.
48

Get List of Orders

Action

In Zapier“Returns a list of orders belonging to box office.”

Returns the box office's orders as a list, no ID needed.

When to use it
an organiser sending a daily-style digest of sales to a reporting sheet, triggered by another event.
Watch out
without a search step there is no filtering here by buyer email.
49

Update Order

Action

In Zapier“Updates an existing order”

Edits an existing order, identified by its or_ code. When the trigger did not carry that code, Get List of Orders is where to find it.

When to use it
a school trip organiser correcting a buyer's details once the parent sends them through a form.
Watch out
behind Order Updated it retriggers the Zap.
50

Create Override

Action

In Zapier“Create an override for the given event series id.”

Sets an exception on a series for one ticket type, ticket group or bundle, identified by its tt_, tg_ or bu_ code. The series ID is required as well.

When to use it
a theatre adjusting one tier for a single run without touching the rest of the series.
51

Update Override

Action

In Zapier“Update existing override.”

Edits an override already set on a series. It requires the series ID and the override ID, which starts with ov_.

When to use it
a theatre extending a special tier for one run after a decision recorded in its planning board.
52

Create Product

Action

In Zapier“Create a new product.”

Adds a product to your box office. A name and a price in cents are the only mandatory fields. Get List of Products then returns it along with the pr_ code the other product actions ask for.

When to use it
a dinner club adding a merchandise item to its box office from its stock tool.
53

Delete Product

Action

In Zapier“Delete a product. This action is irreversible. The product will be permanently removed.”

Erases an add-on product from its pr_ code, with no way back. Ticket Tailor flags the removal as permanent, so check the code with Get Product before wiring it to a live trigger.

When to use it
a gala team removing a sold-out merchandise item as soon as its stock tool marks it as gone.
54

Get Product

Action

In Zapier“Returns a single product; all currency values are in cents (or equivalent), with no decimals.”

Reads one product from its pr_ code, with the price in cents, so another tool can work with the same figure as the box office.

When to use it
a dinner club pulling a product's price into its stock tracker each time an order includes it.
55

Get List of Products

Action

In Zapier“Returns a list of products.”

Brings back the products of your box office, with no ID required. Each one comes with the price in cents and the pr_ code other actions want.

When to use it
a festival syncing its merchandise range to an inventory sheet when a new event is created.
56

Update Product

Action

In Zapier“Updates an existing product.”

Changes a product you already have, located by its pr_ code. Any price you send is in cents, like everywhere else in Ticket Tailor.

When to use it
a gala dinner adjusting its table-wine product as supplier prices move in the purchasing tool.
Watch out
a price typed in whole units comes out far too low.
57

Get Store

Action

In Zapier“Returns store configuration.”

Returns the configuration of one store, from its st_ code. It reads only; nothing changes in the store.

When to use it
an agency comparing settings across the stores it runs for clients, before applying a change with Update Store on any of them.
58

Get List of Stores

Action

In Zapier“Returns a list of stores.”

Shows the stores tied to your account, no ID required, which gives you the st_ codes that Get Store and Update Store need.

When to use it
a multi-venue group mapping its stores before building one Zap per venue, so each Zap targets the right store.
59

Update Store

Action

In Zapier“Updates store configuration.”

Changes the configuration of one store, found through its ID starting with st_.

When to use it
an agency running several box offices that keeps store settings aligned from one central sheet.
Watch out
this touches store-wide settings, so test it on one store first.
60

Create Ticket Group

Action

In Zapier“Create a ticket group for the given event series id.”

Creates a group inside a series, which ticket types and bundles can then belong to. A series ID and a group name are all it asks for.

When to use it
a conference that adds a Workshops group to each new edition before loading the sessions.
61

Delete Ticket Group

Action

In Zapier“Delete a ticket group. This action is irreversible. The ticket group will be permanently removed and any ticket types or bundles in the group will be removed from the group.”

Deletes a ticket group of a series. The ticket types and bundles it held are taken out of the group, not deleted.

When to use it
a conference dissolving a workshop group once sessions are merged.
Watch out
the group itself cannot be restored.
62

Update Ticket Group

Action

In Zapier“Update existing ticket group.”

Renames or edits a ticket group within a series. It needs the series ID and the group ID, which begins with tg_.

When to use it
a festival rebranding its VIP group once a sponsor's name is confirmed by the partnerships team.
63

Create Ticket Type

Action

In Zapier“Create a ticket type for the given event series id.”

Puts a new kind of ticket on sale in a series, such as General Admission. It needs the series ID, a name, a price in cents and the quantity on offer.

When to use it
a festival that opens a late-release tier from a decision logged in its planning sheet.
Watch out
the price field counts cents, so a price typed as if it were in whole units ends up a hundred times too low.
64

Delete Ticket Type

Action

In Zapier“Delete a ticket type. This action is irreversible. The ticket type will be permanently removed.”

Takes a ticket type off a series for good, from the series ID and the tt_ code.

When to use it
a festival withdrawing an early-bird tier that was created by mistake by another Zap.
Watch out
the deletion is permanent and cannot be undone.
65

Update Ticket Type

Action

In Zapier“Update existing ticket type.”

Adjusts a ticket type already on sale, found through its series ID and its tt_ code. Prices you change are in cents.

When to use it
a club raising the price of its door tickets once early sales hit the level set in a tracking sheet.
66

Get List of Voucher Codes

Action

In Zapier“Returns a list of voucher codes.”

Lists the individual codes attached to one voucher, from its vo_ code. That is the step to use when a voucher carries several codes for different people.

When to use it
a corporate events team sending each client the batch of codes bought for its staff.
67

Void Voucher Code

Action

In Zapier“Mark a voucher code as voided. This action is irreversible. This will only mark one voucher code as voided, and will not impact the other related codes.”

Voids a single code of a voucher, leaving the other codes of the same voucher untouched. It needs the voucher ID and the code ID starting with vc_.

When to use it
a theatre cancelling one leaked gift code.
Watch out
irreversible.
68

Create Voucher

Action

In Zapier“Creates a new voucher and the associated voucher codes, if given.”

Creates a voucher worth a set value, plus its codes if you supply them. The name and value are mandatory, and the value is written in cents.

When to use it
a cookery school thanking every large order with credit for its next class.
Watch out
typing 10 creates a voucher worth ten cents, not ten units.
69

Delete Voucher

Action

In Zapier“Delete voucher and its associated voucher codes. This action is irreversible. The voucher and its voucher codes will be permanently removed.”

Deletes a voucher together with every code attached to it, from the vo_ identifier. Nothing of that voucher remains afterwards.

When to use it
a finance team clearing test vouchers before the season opens.
Watch out
to cancel only one code, use Void Voucher Code instead.
70

Get Voucher

Action

In Zapier“Returns a single voucher; all currency values are in cents (or equivalent), with no decimals.”

Reads one voucher from its vo_ code, with its value in cents, and passes it to the next step.

When to use it
a gift shop desk checking a voucher's value when a customer asks by email, without anyone logging into the box office.
Watch out
divide by a hundred before showing the value.
71

Get List of Vouchers

Action

In Zapier“Returns a list of vouchers.”

Pulls every voucher you have created into one list, with no ID to provide. To see the individual codes of one voucher, Get List of Voucher Codes is the step to use.

When to use it
a finance team reconciling outstanding gift credit at the end of a season, before the books close.
72

Update Voucher

Action

In Zapier“Update an exiting voucher. If any voucher codes are given, create new voucher codes and associate them with the voucher.”

Changes a voucher identified by its vo_ code, and creates any new codes you supply, attached to that voucher.

When to use it
a theatre adding fresh codes to its gift voucher every time a new batch is sold elsewhere.
73

Delete Waitlist Signup

Action

In Zapier“Deletes a waitlist signup. This action is irreversible.”

Takes one person off the waitlist of a series. It needs the series ID and the signup ID starting with wa_.

When to use it
a comedy club removing fans who already bought for the extra night.
Watch out
irreversible.
74

Get List of Waitlist Signups

Action

In Zapier“Returns a list of waitlist signups.”

Gives you everyone waiting on one event series, from its es_ code. Unlike the waitlist trigger, it returns the whole queue at once.

When to use it
a comedy club that wants the full queue for a sold-out run before deciding to add an extra night with Create Event Occurrence.
When it breaks

When a Ticket Tailor Zap breaks

Zapier lists no help article and no rate limit specific to Ticket Tailor. So what breaks is the general stuff (and, luckily, it breaks in ways you can see coming).

Four situations account for the surprises worth knowing before you publish. If a Zap already misbehaves, the Zapier troubleshooting page walks through the fixes.

  • Past orders never come through

    A Zap only reacts to what happens after you publish it. Orders, tickets and memberships created before that stay where they are, and moving them is a separate job.

  • The Zap keeps setting itself off

    Order Updated followed by Update Order on the same order writes into what the trigger watches. The Zap fires again, and again, and burns through your tasks.

  • A bulk import gets held back

    Importing hundreds of tickets or memberships at once can produce a huge batch, which Zapier's flood protection may hold back instead of running.

  • A delete you cannot undo

    Most Delete actions, Void Issued Ticket and Void Voucher Code are irreversible on the Ticket Tailor side. Test them on a dummy item before putting them behind a live trigger.
Need help

Need help automating Ticket Tailor with Zapier?

A person reads every message.

FAQ

Questions about the Ticket Tailor Zapier integration

01Is the Ticket Tailor Zapier integration free?
Yes, as far as Zapier goes. Ticket Tailor is not a premium app, so it works on the free plan, which gives you 100 tasks a month and as many Zaps as you like. The catch is size: on the free plan each Zap holds one trigger and one action, nothing more. The moment you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. One action carries its own charge on the Ticket Tailor side: Create Issued Ticket (Fees Apply) costs a fee per ticket, even a free one.
02How many Zapier tasks does a Ticket Tailor Zap use?
One task for each action that succeeds, and nothing for the trigger. A Zap built on Order Created with a single Create Voucher action costs one task per order. Put three actions behind it and the same order costs three. An action that fails is not billed. Watch Issued Ticket Created in particular: it runs once per ticket, not per order, so a group booking of six tickets triggers six runs and six times the tasks of every action that follows.
03Does the Ticket Tailor trigger work in real time?
Yes. All ten Ticket Tailor triggers are instant: Ticket Tailor tells Zapier the moment the event happens, so the Zap starts straight away. The interval grid of Zapier plans, 15 minutes on Free and 2 on Professional, only applies to polling triggers, and this app has none. That makes Ticket Tailor one of the apps where the free plan feels the same as a paid one on speed. In the editor, a Zap started by an instant trigger shows a lightning bolt.
04What does it take to connect Ticket Tailor to Zapier?
A Ticket Tailor account and a Zapier account, nothing else. In Zapier you open Apps, click + Add connection, search for Ticket Tailor and click Add connection. A tab opens where you sign in to Ticket Tailor and grant access. If a Zap will touch box offices or items that someone else owns, your account needs read or write access to them. Once made, the connection is reused by every Ticket Tailor step in every Zap you build.
05Why does a Ticket Tailor price or voucher come out a hundred times too small?
Because Ticket Tailor works in cents, with no decimals. Every price, voucher value and order amount, in triggers and actions alike, is a whole number of cents or the equivalent in your currency. Typing 10 into the value of Create Voucher creates a ten-cent voucher, not a ten-unit one. The same goes for a filter on Order Created: set the threshold in cents, and pick a number rule, because a text rule applied to an amount would never pass. Prices in Create Ticket Type, Create Product and Create Bundle follow the same logic.
06What if the Ticket Tailor action you need is not in Zapier?
Check the list of 74 actions first: most objects come with create, update, get and delete versions. What the integration lacks is a search step, so finding an order or a ticket from an attendee's email is not possible directly. Get List of Orders and the other list actions are the closest workaround, since they return everything and let a later step pick. If the operation still is not there, the Zapier page of the app is the place to check whether it has been added since.
07Zapier, Make or n8n for Ticket Tailor?
There is no single winner, only criteria. On Zapier, Ticket Tailor offers 84 ready operations and all ten triggers are instant on every plan, including the free one. The free plan caps each Zap at two steps and 100 tasks a month, so your monthly volume of orders and the number of steps per automation decide whether a paid plan is needed. Make and n8n each have their own model; compare them on the same two criteria, volume and steps, before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations