Resources · Make integration

Ticket Tailor Make integrationAutomate Ticket Tailor with Make.

Every ticket sold can start a workflow on its own. The Ticket Tailor Make integration gives you six modules: one trigger for new orders, three actions and two searches. This guide links your account, builds a first scenario with you and explains each module.

Try the Ticket Tailor integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ticket Tailor Make integration do for you?

It lets Make read your Ticket Tailor box office without any code. A scenario, the automation you build in Make, can notice each new order and pull the order or event details, then hand them to the rest of your tools. Ticket Tailor stays where you sell; Make carries the data onward.

A buyer list that fills itself. Put Watch New Orders at the start of a scenario and every fresh purchase travels to your spreadsheet or CRM as it is picked up, with no copy and paste after each sale.

Event context next to each sale. An order alone rarely tells your team enough. Chain Get an Event after the trigger so the event details ride along with the order, ready for a message to the venue crew or a note in your project tool.

A full sweep when you need one. List Events and List Orders return several items at once, which suits a reconciliation or a report built from everything already sold.

Know the edges before you start: going by their names and descriptions, the listed modules read data; none creates or edits an order or an event. For anything else in the Ticket Tailor API, Make an API Call reuses the same connection. If you are still choosing a platform, the n8n vs Make comparison lays out the differences, and the Make pricing guide explains how operations are counted. Teams that prefer to hand the build over can talk to our Make agency.

Connect

How do you connect Ticket Tailor to Make?

  1. 01

    Copy your API key in Ticket Tailor

    You need an active Ticket Tailor account. In the dashboard, open Settings, click API keys and copy the key shown on screen. Keep that tab open until the connection works.

  2. 02

    Add a Ticket Tailor module in Make

    In your scenario, add any Ticket Tailor module and click Create a connection. A connection is your Ticket Tailor account linked to Make once, then reused by every Ticket Tailor module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several box offices. Paste the API key you copied, or follow the instructions Make shows on screen, then save.

First scenario

Your first scenario: each new order arrives with its event details

GoalWhen a new order is created in Ticket Tailor, Make fetches the event it belongs to so both travel together.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Place the trigger

    Search for Ticket Tailor, pick Watch New Orders and link your account with Create a connection. This module is the scenario's starting point.

  3. 03

    Add Get an Event

    Click the + on the right of the trigger, choose Get an Event, then pick the event in the order bundle, the item the trigger passed along. Run once shows whether the order carries a reference to its event.

  4. 04

    Test with Run once

    Click Run once to test the scenario one time, then read the bundles each module received: you see at a glance whether the event came back.

  5. 05

    Schedule and switch on

    Set the clock on the first module, every 15 minutes by default, and switch the scenario on. From then on, new orders get picked up at that rhythm.

Triggers

What starts a Ticket Tailor scenario

1 module starts a scenario when something happens in Ticket Tailor. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Ticket Tailor as soon as it happens.

Ticket Tailor1Watch New Orders

Watch New Orders

Scheduled trigger

In Make“Triggers when a new order is created.”

Each time someone buys a ticket, this trigger hands the new order to your scenario as a bundle, one bundle per order, so the steps after it can file, share or enrich the sale without anyone touching the dashboard.

How it fires
scheduled. Make checks Ticket Tailor on the scenario's schedule, shown by the clock badge, rather than being called the moment a sale happens.
When to use it
as the first module whenever a sale should start something elsewhere, like a thank-you email or a row in your attendee sheet.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so a fresh order waits for the next check before your scenario sees it.
Modules

What the Ticket Tailor modules do

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

Ticket Tailor1

Get an Event

Action

In Make“Gets an event.”

You get the full record of one event, so the rest of the scenario can quote its details instead of a bare reference. It is an action that works on a single event.

When to use it
right after Watch New Orders, when a confirmation or a staff alert should mention the event the buyer chose.
Watch out
it needs to know which event you mean; map it from the previous module rather than typing it by hand.
Ticket Tailor2

Get an Order

Action

In Make“Gets an order.”

This module brings back one specific order, which is handy when another app only gives you a pointer to a sale and you need the complete purchase in hand.

When to use it
a support form or a payment tool mentions an order, and your scenario must look it up before replying or updating a record.
Watch out
it returns a single order; for a batch of sales, List Orders is the right pick.
Ticket Tailor3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Ticket Tailor API through the connection you already built, which covers whatever the five other modules leave out.

When to use it
the task you have in mind has no dedicated module, for example writing to Ticket Tailor instead of reading, if its API offers that endpoint.
Watch out
you describe the request yourself, so keep the vendor's API documentation open while you set it up.
Ticket Tailor4

List Events

Search

In Make“Gets a list of events.”

Your scenario receives your events as a set of bundles, one per event, which gives you the whole lineup to sort, filter or copy in a single pass.

When to use it
building a calendar page, a shared sheet or a report that needs every event rather than just one.
Watch out
a search can return zero, one or many bundles, and each bundle makes the next module run again, which uses more operations.
Ticket Tailor5

List Orders

Search

In Make“Gets a list of orders.”

Here the scenario gets a whole batch of orders back as separate bundles, which is what you want for totals, checks or a clean export of past sales.

When to use it
reconciling ticket sales with your accounting tool, or catching up on orders placed before the scenario existed.
Watch out
if nothing matches, the module returns zero bundles and the steps after it simply do not run, which can look like a silent failure.
Need help

Need help automating Ticket Tailor with Make?

A person reads every message.

FAQ

Questions about the Ticket Tailor Make integration

01Is the Ticket Tailor Make integration free?
Yes, on the Make side. Ticket Tailor is a standard app, so it is available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your Ticket Tailor subscription is a separate matter, and its price depends on Ticket Tailor, not on Make.
02What is needed to connect Ticket Tailor to Make?
Two things: an active Ticket Tailor account and an API key from it. You find the key in the Ticket Tailor dashboard under Settings, then API keys. In Make, add any Ticket Tailor module, click Create a connection, give the connection a name if you like and paste the key. That single connection then serves every Ticket Tailor module in all your scenarios, so you only do this once per account.
03Does the Ticket Tailor trigger in Make work in real time?
No. Watch New Orders is a scheduled trigger: Make checks Ticket Tailor on the scenario's schedule instead of being notified when a sale happens. A new scenario runs every 15 minutes by default. Paid plans let you tighten that to 1 minute, while the Free plan keeps 15 minutes as the minimum. For most sales follow-ups that delay is fine, but plan for it when a message must go out right after purchase.
04What if a Ticket Tailor module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Ticket Tailor API with the connection you already set up, which fills the gaps left by the six listed modules. That matters here because the dedicated modules mostly read data: they watch, get and list orders and events. Anything else the Ticket Tailor API exposes, writing included if an endpoint allows it, goes through that module, with the vendor's API documentation open next to the editor as your guide.
05Should Ticket Tailor be automated with Make or n8n?
It depends on the tool your team already knows. On Make, Ticket Tailor offers a scheduled trigger for new orders, actions to get an event or an order, searches to list both, and Make an API Call for the rest, all available from the Free plan. The same app often has an n8n node too, so check that side before deciding. Compare the modules each tool offers against your use case rather than looking for a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations