Resources · Make integration

SimpleTix Make integrationAutomate SimpleTix with Make.

Every ticket sale, check-in or abandoned cart in SimpleTix can start work elsewhere, on its own. The SimpleTix Make integration offers 9 instant triggers and no actions. This guide shows event teams how to connect the account and build a first scenario.

Try the SimpleTix integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SimpleTix Make integration automate?

The SimpleTix Make integration lets things that happen in your ticketing account start a scenario, the automation you build in Make as a chain of modules (bricks, each doing one job). SimpleTix only brings the starting point: nine instant triggers, which SimpleTix calls through a webhook the moment an order, attendee or event appears. What happens next is done by modules of your other apps.

Win back abandoned carts. Watch Abandoned Cart Orders hands Make each buyer who left before paying. Send that bundle (one item passed from module to module, here one cart) to your email tool and someone can follow up while the buyer still remembers the show.

Keep a guest list that fills itself. Watch New Attendees hands Make each new guest, and the next module adds one row per person to a base, as the Airtable Make integration guide shows.

Know who is at the door. Watch Attendees Check-In and Watch Attendees Check-Out feed a live attendance sheet, useful for a venue that has to track who is still inside.

What Make does not do here: the app has no action or search module and no Make an API Call module, so Make cannot create an order or edit an event in SimpleTix. Make also says its SimpleTix documentation is limited, so test each trigger before relying on its data. If this is your first scenario, the Make training covers the editor basics.

Hesitating between tools? The n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect SimpleTix to Make?

  1. 01

    Add a SimpleTix trigger

    In your scenario, click the +, search for SimpleTix and pick the trigger you need, for example Watch New Orders. Make then asks for a connection, meaning your SimpleTix account linked to Make once and reused by every SimpleTix module.

  2. 02

    Create the connection

    Click Create a connection. Give it a clear name if you manage several SimpleTix accounts, then authorize Make on the SimpleTix page that opens, or paste the key SimpleTix gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and every other SimpleTix trigger you add later can reuse it without logging in again. Close the module settings and move on to the next step of your scenario.

First scenario

Your first scenario with SimpleTix

GoalWhen a new order is created in SimpleTix, Make adds the sale to another app, such as a sales sheet.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Pick Watch New Orders

    Search for SimpleTix, choose Watch New Orders and select your connection. This instant trigger waits for SimpleTix to call Make each time an order is created.

  3. 03

    Add the destination

    Click the + on the right of the SimpleTix module and add a module from the app that should receive the sale. Map the order data from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once, then place a test order in SimpleTix. Open the bubbles above each module to read the bundles they received and check the mapping.

  5. 05

    Switch it on

    Save and switch the scenario on. From then on, each new order reaches Make through the webhook as soon as SimpleTix records it, with no action on your side.

Triggers

SimpleTix triggers in Make

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

SimpleTix1Watch Abandoned Cart Orders

Watch Abandoned Cart Orders

Instant trigger

In Make“Triggers when customer abandons their shopping cart without completing the purchase, capturing potentially lost sales opportunity.”

You get a bundle each time a buyer fills a cart on your SimpleTix page and leaves before paying, so a sale you were about to lose lands in Make while it can still be saved.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the cart is abandoned.
When to use it
to pass the lost cart to your email tool or CRM so someone on the team follows up with that buyer.
Watch out
Make's SimpleTix documentation is limited, so run the scenario once on a real abandoned cart and read the bundle before mapping anything downstream.
SimpleTix2Watch API Errors

Watch API Errors

Instant trigger

In Make“This trigger is just to test Scenario with an API Error”

This one is a testing aid: it shows how your scenario behaves when SimpleTix returns an API error, instead of waiting for a real failure to find out.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the error happens.
When to use it
while building, to check that the module you placed after it, an alert or a log, does what you expect before live sales go through.
Watch out
the official description presents it as a test trigger only, so keep it out of the scenarios that should react to real sales or attendees.
SimpleTix3Watch Attendees Check-In

Watch Attendees Check-In

Instant trigger

In Make“Triggers when an attendee check-in.”

Every guest checked in at your event becomes a bundle in Make, the moment SimpleTix records the check-in, which gives you a live view of who has arrived.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the attendee checks in.
When to use it
to update an attendance sheet during the event, or to ping the organizer when an expected guest walks in.
Watch out
arrival and departure are two separate triggers. If you need both, build a second scenario with Watch Attendees Check-Out rather than expecting this module to report exits.
SimpleTix4Watch Attendees Check-Out

Watch Attendees Check-Out

Instant trigger

In Make“Triggers when an attendee check-out.”

Here Make learns about the other end of the visit: it receives each attendee who checks out of an event in SimpleTix, one bundle per person.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the check-out is recorded.
When to use it
for venues that must know who has left, paired with the check-in trigger to keep a head count of people still inside.
Watch out
a guest who leaves without checking out never starts this trigger, so a count built on it alone will not match the room.
SimpleTix5Watch New Attendees

Watch New Attendees

Instant trigger

In Make“Triggers when a new attendee added.”

Your guest list can grow on its own: this trigger delivers a fresh bundle whenever a person is added as an attendee in SimpleTix, ready to copy into the tools where the team prepares the event.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the attendee is added.
When to use it
to fill a guest list in a spreadsheet, or to add each attendee to a welcome email sequence.
Watch out
SimpleTix offers a separate trigger for orders. Pick Watch New Orders when the purchase matters, this one when the person matters.
SimpleTix6Watch New Events

Watch New Events

Instant trigger

In Make“Triggers when a new event is created and a new time added.”

Publishing a new event, or adding a new time to one, is enough for Make to hear about it, so the rest of your tools learn about the date without a copy and paste.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the event or the new time is created.
When to use it
to post the new date in your team chat, or to create a matching entry in your planning calendar.
Watch out
the official description covers both a new event and a new time, so a show with extra dates can start the scenario more than once. Plan for that in the next modules.
SimpleTix7Watch New Memberships Purchased

Watch New Memberships Purchased

Instant trigger

In Make“Triggers when a new membership is purchased.”

A new member means a scenario starts: whenever someone buys a membership through SimpleTix, Make receives the purchase and can run your whole welcome routine.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the membership is bought.
When to use it
to add the new member to your CRM, or to alert the person who manages memberships so nothing waits on a manual check.
Watch out
only membership purchases arrive here. Single ticket sales come through Watch New Orders, so do not wait for them in this scenario.
SimpleTix8Watch New Orders

Watch New Orders

Instant trigger

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

Each ticket sale can feed your reporting, accounting or thank-you messages, because this trigger sends every order created in SimpleTix to Make as a bundle.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the order is created.
When to use it
the default starting point when you want one action per sale, such as a new row in a sales sheet.
Watch out
every order runs the whole scenario, and each module run counts as one operation on your Make plan, so a busy on-sale uses operations fast.
SimpleTix9Watch New Wait-List Request

Watch New Wait-List Request

Instant trigger

In Make“Triggers when new wait list request created”

Demand you cannot serve yet stays visible: people who ask to join the waiting list of a sold-out event in SimpleTix reach Make one request at a time.

How it fires
instant. SimpleTix calls Make through a webhook as soon as the request is created.
When to use it
to collect the requests in one shared sheet, or to tell the organizer that a new time might be worth adding.
Watch out
Make only receives the request. Freeing a seat and contacting the person is still up to you or to a module of another app.
Need help

Need help automating SimpleTix with Make?

A person reads every message.

FAQ

SimpleTix and Make: frequent questions

01Is the SimpleTix Make integration free?
Yes. SimpleTix is a standard app in Make, available from the Free plan onward. The Free plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the scenario cap and count usage in operations per month. Your SimpleTix subscription is a separate matter that this page does not cover.
02What do you need to connect SimpleTix to Make?
A SimpleTix account and a Make account. The Make documentation for SimpleTix lists no prerequisites and no specific steps, so the generic flow applies: add a SimpleTix module, click Create a connection, name it if you like, authorize Make on the SimpleTix page or paste the key SimpleTix provides, then click Save. That connection is then reused by all nine triggers. If you run several SimpleTix accounts, create one connection per account and give each a name you will recognize in the module list.
03Do SimpleTix triggers in Make fire in real time?
Yes. All nine SimpleTix triggers are instant: SimpleTix calls Make through a webhook as soon as the order, check-in, event or request happens, none of them is a scheduled trigger that Make checks on a clock. Remember to switch the scenario on, otherwise nothing reaches Make outside of a Run once test. To see it work, click Run once, then create a test order or check in a test attendee in SimpleTix: the bundle shows up in the editor as soon as the webhook call arrives.
04What if the SimpleTix module you need is missing in Make?
It depends on what you need. The app only offers triggers, and it has no Make an API Call module, so Make cannot write to SimpleTix, create an order or update an event. Make also flags its SimpleTix documentation as limited. When a need falls outside the nine triggers, look at whether another app in your stack can do the job, or ask the team for help with the setup.
05Should you use Make or n8n for SimpleTix?
It depends on your criteria. On Make, SimpleTix brings nine instant triggers, no actions and no API call module, which suits reacting to sales, attendees and waitlists. Before choosing, check whether n8n offers a node for SimpleTix and which of your other apps each tool covers, since the scenario will spend most of its work in those. The n8n vs Make comparison linked above sets the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations