Resources · Make integration

TicketPAY Make integrationAutomate TicketPAY with Make.

Want new TicketPAY orders to start work on their own? The TicketPAY Make integration gives you 15 modules: 7 triggers that watch orders, tickets or donations, and 7 list modules. This page shows how to link your account and build a first scenario.

Try the TicketPAY integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TicketPAY Make integration do for you?

The TicketPAY Make integration lets Make read what happens in your ticketing account: new orders, tickets, donations, fees, vouchers, events and transactions. You build a scenario (the automation itself, a chain of modules) and Make runs it on a schedule, with no code.

A trail of every donation. Watch Donations picks up each new gift, so a scenario can pass it on to the tool where your team thanks donors. Each gift travels as a bundle, meaning one item handed from one module to the next.

A clean view of voucher use. When a promotion runs, Watch Vouchers or List Vouchers brings the codes into Make, where you can compare them with what was actually sold through List Orders.

Finance data without exports. Watch Transactions and Watch Fees bring in new money movements at each scheduled check, which spares someone the job of downloading files by hand.

Know the limits before you start. The public documentation for TicketPAY on Make is thin: it lists the modules but gives no descriptions and no connection details. Anything the other named modules do not cover goes through Make an API Call. If you are still weighing tools, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect TicketPAY to Make?

  1. 01

    Add a TicketPAY module

    In a new scenario, click the +, search for TicketPAY and pick any module, for instance Watch Orders. Then click Create a connection. A connection is your TicketPAY account linked to Make once and reused by every TicketPAY module.

  2. 02

    Name the connection

    This step is optional, yet worth a few keystrokes. Give the connection a name that says which TicketPAY account it points to, so nobody picks the wrong one later when several people build scenarios in the same Make team.

  3. 03

    Authorize and save

    Depending on what TicketPAY asks, either approve Make on the TicketPAY page that opens, or paste the key TicketPAY gives you. Finish with Save. Make can now list the TicketPAY data this module reads.

First scenario

Your first scenario with TicketPAY

GoalWhen a new order lands in TicketPAY, Make also pulls the ticket list, so one test run shows you what orders and tickets carry.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for TicketPAY and choose Watch Orders as the first module, the one that starts everything.

  2. 02

    Link your account

    Click Create a connection and follow the steps above. Once the connection exists, Make shows the options it can read from TicketPAY, so you fill the module instead of guessing values.

  3. 03

    Add List Tickets

    Click the + on the right of Watch Orders, pick TicketPAY again, then List Tickets. Fill only the fields Make shows you: the documentation lists none, so do not guess them.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open them: with a thin documentation, this is where you learn what TicketPAY really sends.

  5. 05

    Schedule and switch on

    Set the clock on Watch Orders. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Triggers

What starts a TicketPAY scenario?

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

TicketPAY1Watch Donations

Watch Donations

triggerIn the docs only

Watch Donations hands each new donation recorded in TicketPAY to your scenario, one bundle per gift, so a thank-you or a record in another tool can follow without anyone copying data by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
a charity gala where every gift should reach the fundraising team's list.
Watch out
the documentation gives no description of this trigger, so run it once and read the bundle before building on it.
TicketPAY2Watch Events

Watch Events

triggerIn the docs only

Your scenario learns about each event added in TicketPAY through Watch Events. Planning, promotion or staffing work can then start from a single source instead of a copied spreadsheet.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new event shows up at the next check, not the second it is saved.
When to use it
a venue that announces each new show to its marketing tool.
Watch out
its type is inferred from the module name; confirm on the clock badge in the editor.
TicketPAY3Watch Fees

Watch Fees

triggerIn the docs only

With Watch Fees, the fees TicketPAY records reach Make at each check of the scenario, which gives your bookkeeping a steady feed without anyone exporting a file.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along whatever is new since the previous check.
When to use it
a finance lead who wants every fee logged in the accounting sheet.
Watch out
the Make documentation does not say what a fee record contains, so inspect the first bundle with Run once before you map anything.
TicketPAY4Watch Orders

Watch Orders

triggerIn the docs only

Watch Orders is the natural starting point: every new purchase in TicketPAY becomes a bundle in Make, ready to feed a confirmation, a CRM record or a sales report.

How it fires
scheduled. Make checks the app on the scenario's schedule; on the Free plan, the shortest gap between two checks is 15 minutes.
When to use it
when each sale should reach the customer file or a team alert.
Watch out
every order counts as operations, so a busy on-sale uses your plan faster.
TicketPAY5Watch Tickets

Watch Tickets

triggerIn the docs only

Where Watch Orders sees the purchase, Watch Tickets sees each ticket issued, which is the level you need for anything done per attendee: a badge, a seat list, a check-in sheet.

How it fires
scheduled. Make checks the app on the scenario's schedule rather than being alerted by TicketPAY.
When to use it
a conference that builds its attendee list one ticket at a time.
Watch out
each ticket arrives as its own bundle, and every module that handles it afterwards uses operations.
TicketPAY6Watch Transactions

Watch Transactions

triggerIn the docs only

Payment movements in TicketPAY reach your scenario through Watch Transactions, so reconciliation work can start from the data itself instead of a monthly download.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up the transactions recorded since its last pass.
When to use it
matching ticket revenue against what lands in the bank.
Watch out
the documentation does not say how transactions relate to orders, so compare a few bundles of each before you build on one of them.
TicketPAY7Watch Vouchers

Watch Vouchers

triggerIn the docs only

Each voucher created in TicketPAY can kick off a scenario through Watch Vouchers, handy when discount codes need to reach a partner, a newsletter or an internal tracker.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a code shows up after the next check.
When to use it
a promoter who sends partner codes shortly after the box office creates them, at the next check.
Watch out
the documentation says nothing about voucher fields; confirm what each bundle carries with Run once.
Modules

What else can TicketPAY do in Make?

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

TicketPAY1

List Donations

SearchIn the docs only

List Donations returns the donations already in TicketPAY, one bundle each, which is what you want to rebuild a donor file or check totals after the fact.

When to use it
a one-off import of past gifts before Watch Donations takes over.
Watch out
a search can return zero, one or many bundles, and every bundle processed later counts.
TicketPAY2

List Events

SearchIn the docs only

Pull your full TicketPAY event catalog into a scenario with List Events, useful to keep a website calendar or a planning sheet in line with the box office.

When to use it
started from another app or a schedule, when you need every event, not only new ones.
Watch out
the result can hold zero events, so test that case with Run once before you rely on the scenario.
TicketPAY3

List Fees

SearchIn the docs only

Fees stored in TicketPAY come back as a list here, handy for a full review of charges, where Watch Fees only brings the new ones.

When to use it
when an accountant asks for the complete fee history in a spreadsheet.
Watch out
the documentation does not say which filters the module offers, so check the fields in the editor.
TicketPAY4

List Orders

SearchIn the docs only

Reach for List Orders to get back the orders already in TicketPAY: a way to fill a report or a CRM with sales that happened before your scenario existed.

When to use it
a first catch-up import, then Watch Orders for what comes next.
Watch out
a large history means many bundles and as many operations in the following modules.
TicketPAY5

List Tickets

SearchIn the docs only

List Tickets gives you tickets as separate bundles, the right grain when a door list, a seat plan or a badge run must hold one line per attendee.

When to use it
just before an event, to produce the final attendee list in one go.
Watch out
run it once and look at the bundles to see which details TicketPAY returns.
TicketPAY6

List Transactions

SearchIn the docs only

Need the money trail in bulk? List Transactions brings back recorded payments so a scenario can write them to a ledger or a finance tool in one pass.

When to use it
closing the books after an event, when every payment must be accounted for.
Watch out
compare with List Orders on a sample first, so the same sale is not booked twice.
TicketPAY7

List Vouchers

SearchIn the docs only

This module lists the vouchers that exist in TicketPAY, which helps you audit promotions or send a partner the full set of codes they received.

When to use it
at the end of a campaign, to see every code issued in one table.
Watch out
nothing in the documentation says whether used and unused codes are told apart; check the bundles.
TicketPAY8

Make an API Call

ActionIn the docs only

Make an API Call is the way out when the other named modules fall short: it calls any endpoint of the TicketPAY API with the same connection, so you can reach data or actions the list does not show.

When to use it
when you need to create or update something in TicketPAY, since the other modules only watch or list data.
Watch out
you need the TicketPAY API reference, since Make does not document the endpoints.
Need help

Need help automating TicketPAY with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the TicketPAY Make integration free?
Yes, TicketPAY is a standard app, so it works from the Make Free plan. That plan has real limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle. Nothing here covers what TicketPAY itself may charge.
02What do you need to connect TicketPAY to Make?
A TicketPAY account and a Make account. The Make documentation lists no prerequisite and no dedicated connection steps for TicketPAY, so the generic flow applies: add a TicketPAY module, click Create a connection, optionally name it, authorize Make on the TicketPAY page or paste the key TicketPAY provides, then Save. The same connection then serves every TicketPAY module in your scenarios. If TicketPAY asks for a key you cannot find, look in your account settings or ask TicketPAY support, since Make gives no detail on this.
03Do TicketPAY triggers in Make fire in real time?
No. All 7 TicketPAY triggers are scheduled, and none is instant. Make checks TicketPAY on the scenario's schedule, every 15 minutes by default, and passes along what changed since the previous check. On the Free plan, 15 minutes is the shortest gap between two checks. Paid plans can go down to 1 minute. Note that the type of each trigger is inferred from its name, as the Make documentation gives no description, so confirm the clock badge on the module in the editor.
04What if a TicketPAY module is missing in Make?
Use Make an API Call. It calls any endpoint of the TicketPAY API with your existing connection, which covers what the other named modules do not. That matters here, because every listed module only reads data: the 7 triggers watch for new items and the 7 list modules return existing ones. To create or update something in TicketPAY, the API call is the route. Keep in mind that the Make documentation for TicketPAY is limited, so you need the TicketPAY API reference to know which endpoint to call.
05Should you use Make or n8n for TicketPAY?
It depends on what you need. On Make, TicketPAY has 15 modules: 7 scheduled triggers, 7 list modules and Make an API Call, which is enough to read orders, tickets, donations and payments without code. Before choosing n8n, check that a TicketPAY node exists there and what it covers, because this page cannot confirm it. Then compare the two on the criteria that matter to your team, such as how you want to build and who maintains the scenarios, rather than on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations