Resources · Make integration

Eventbrite Make integrationAutomate Eventbrite with Make.

Every ticket sold on Eventbrite can start work in your other tools. The Eventbrite Make integration gives you 17 modules: 6 triggers, 5 actions and 6 searches. This guide takes organizers who are new to Make from the connection to a first working scenario.

Try the Eventbrite integration on Make See the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Eventbrite Make integration do for you?

The Eventbrite Make integration links your Eventbrite account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, acts or searches. Here, those modules catch new orders and attendees, create and publish events, and pull lists of orders or ticket classes for your other apps.

Alert the team on each sale. Watch Orders is the only instant trigger of the set: Eventbrite calls Make as soon as someone buys tickets for the event you picked, and the next module can post the order in a chat channel or add the buyer to your CRM.

Keep the guest list where you work. Watch Attendees picks up each new sign-up on one event, and Watch Attendees In Organization does the same across every event of an organization. Each attendee travels as one bundle, the item passed from a module to the next, toward a spreadsheet or an email tool.

Launch an event from your planning file. Create an Event sets it up, Create a Ticket Class adds the ticket types, and Publish an Event puts it on sale when you are ready. Unpublish an Event takes it back off.

What Make does not give you here is complete documentation: its help page for Eventbrite is marked as limited. Test each module with Run once, the button that runs the scenario one time, before you rely on it. The same app also has an n8n node, covered on the Eventbrite n8n integration page, and n8n vs Make lays out how the two tools differ. For a guided start with the editor, see Make training.

Connect

How do you connect Eventbrite to Make?

01
Add an Eventbrite module
Open your scenario, click the +, search for Eventbrite and pick any of its modules. In the module panel, click Create a connection. A connection is your Eventbrite account linked to Make once, then reused by all 17 modules.
02
Name the connection
Make offers a default name. Keep it, or type something clearer, such as the organizer account it points to. That small step pays off when a team handles more than one Eventbrite account from the same Make login.
03
Authorize Make and save
Follow the step Eventbrite asks for: authorize Make on its page, or paste the key it gives you. Then click Save. Back in the module, Make can now show the events and objects that account is allowed to read.

First scenario

Your first scenario: from a planning row to an Eventbrite event

GoalWhen a new event appears in your planning tool, Make creates it in Eventbrite and adds its first ticket class.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. Start with the app where your team plans events, a spreadsheet or a form, and pick its trigger for new entries.
02
Add Create an Event
Click the + on the right of that first module, search Eventbrite and choose Create an Event. Select your connection, then map the planned event details from the first module into the fields Make shows.
03
Add Create a Ticket Class
Add a third module, Create a Ticket Class. Point it at the event the previous module just created by mapping its output, then fill in the ticket details your planning row holds.
04
Test with Run once
Add a test row in your planning tool, then click Run once. Open each module to read the bundle it received, and look at the new event in Eventbrite before going further.
05
Schedule and switch on
Click the clock on the first module. A new scenario runs every 15 minutes by default; keep that or change it, then switch the scenario on. Each planned event now lands in Eventbrite with its first ticket type.

Triggers

Which Eventbrite triggers start a scenario?

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

Eventbrite1Watch Attendees

Watch Attendees

Scheduled trigger

In Make“Triggers when a new attendee is signed up to a specified event.”

Watch Attendees hands your scenario every new person who signs up for one event you choose, so the guest list can live wherever your team needs it.

How it fires

scheduled. Make checks Eventbrite on the scenario's schedule, every 15 minutes by default, and picks up the new attendees.

When to use it

a workshop where each registrant should land in your mailing tool or in a shared sheet.

Watch out

it follows a single event. To cover every event of an organization with one scenario, take Watch Attendees In Organization instead.

Eventbrite2Watch Attendees In Organization

Watch Attendees In Organization

Scheduled trigger

In Make“Triggers when a new attendee is signed up to an event in the given organization.”

With this trigger, one scenario collects the sign-ups of every event run by an organization, not just one listing.

How it fires

scheduled. Make asks Eventbrite for new attendees each time the scenario runs, on the schedule set on the first module.

When to use it

you run many events and want a single contact base fed by all of them, without building one scenario per event.

Watch out

each attendee is one bundle, and each module that handles it spends an operation, the unit Make counts on your plan. A busy organization burns through operations faster.

Eventbrite3Watch Events

Watch Events

Scheduled trigger

In Make“Triggers when a new event matching the specified requirements is found.”

Watch Events tells your scenario that a new event matching your criteria has appeared in Eventbrite, so other tools learn about it without anyone copying details by hand.

How it fires

scheduled. Make looks for new matching events on the scenario's schedule.

When to use it

a colleague creates an event, and the marketing calendar or the events page of your website should pick it up.

Watch out

the criteria you can set appear in the module itself. Since Make's Eventbrite docs are limited, run it once and read what comes back before mapping anything.

Eventbrite4Watch My Orders

Watch My Orders

Scheduled trigger

In Make“Triggers when you place a new order.”

Unlike the other order triggers, this one follows the orders you place yourself as a buyer, not the ones people place for your events.

How it fires

scheduled. Make checks your Eventbrite account for new purchases on the scenario's schedule.

When to use it

you book tickets to trade shows or conferences for your team and want each purchase logged in an expense sheet.

Watch out

if what you want is your own ticket sales, this is the wrong module. Pick Watch Orders or Watch Orders by Event.

Eventbrite5Watch Orders

Watch Orders

Instant trigger

In Make“Triggers when a new order is placed for tickets to a specified event.”

The quickest way to react to a sale: the moment someone buys tickets for the event you picked, Watch Orders starts your scenario.

How it fires

instant. Eventbrite calls Make through a webhook as soon as the order is placed, so nothing waits for a schedule.

When to use it

a thank-you message, a CRM entry or a team alert that should follow the purchase right away.

Watch out

it covers one event per module. For a scheduled version of the same trigger, look at Watch Orders by Event.

Eventbrite6Watch Orders by Event

Watch Orders by Event

Scheduled trigger

In Make“Triggers when a new order is placed for tickets to a specified event.”

New orders for one event reach your scenario here too, but Make fetches them on a schedule instead of waiting for Eventbrite to call.

How it fires

scheduled. Make asks Eventbrite for new orders each time the scenario runs, every 15 minutes by default, 1 minute at the shortest on paid plans.

When to use it

you prefer a scenario that runs at set times, for example to add orders to a sales report sheet.

Watch out

on the Free plan, the gap between two runs is at least 15 minutes. If each sale must trigger an action immediately, Watch Orders is the better pick.

Modules

What can Make do in Eventbrite?

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

Eventbrite1

Create an Event

Action

In Make“Creates a new event.”

Create an Event sets up a new event in your Eventbrite account from data another app already holds, so nobody retypes the details.

When to use it

an approved request in your planning sheet or project tool should become an Eventbrite event.

Watch out

map this module's output into the next ones, because Create a Ticket Class and Publish an Event both work on an existing event.

Eventbrite2

Create a Ticket Class

Action

In Make“Creates a new ticket class.”

A ticket class is one type of ticket on an event, early bird or VIP for instance, and this module adds one to an event that already exists.

When to use it

right after Create an Event, or when a new tier should go on sale for an event already listed.

Watch out

to see which classes an event already has, run List Ticket Classes first and avoid creating duplicates.

Eventbrite3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any part of the Eventbrite API with the connection you already set up, for jobs the other modules do not cover.

When to use it

you need an Eventbrite action that has no dedicated module in this list.

Watch out

you write the request yourself, so keep Eventbrite's API reference open; Make's own Eventbrite docs are limited and will not guide you here.

Eventbrite4

Publish an Event

Action

In Make“Publishes an existing event.”

Publish an Event takes an event you have prepared and makes it public in Eventbrite, the last move of any launch.

When to use it

at the end of a launch scenario, once the event and its ticket classes are in place, or when a manager approves the listing in another tool.

Watch out

the event must already exist, so chain it after Create an Event or after a search that returns that event.

Eventbrite5

Unpublish an Event

Action

In Make“Unpublishes an existing event.”

Taking an event off the public listing without deleting it is the job of Unpublish an Event.

When to use it

a venue falls through, or registrations must pause while the details change.

Watch out

double-check which event the module points to before you switch the scenario on, since the wrong event would vanish from public view.

Eventbrite6

List Attendees

In Make“Retrieves a list of attendees for a specified event.”

List Attendees returns everyone registered for one event, one bundle per person, ready to send to any other app.

When to use it

a speaker asks for the participant list, or you want to send a last reminder through your email tool.

Watch out

a search can return many bundles; every module placed after it runs once per attendee and spends an operation each time.

Eventbrite7

List Orders

In Make“Retrieves a list of all orders for a specified event.”

With List Orders you pull every order placed for one event, which is handy for a sales recap that lives outside Eventbrite.

When to use it

you connect Eventbrite late and need past orders in your spreadsheet before Watch Orders takes over the new ones.

Watch out

it returns all orders, not only new ones, so running it again adds duplicates unless the next module checks for existing rows.

Eventbrite8

List Ticket Classes

In Make“Retrieves a list of ticket classes for a specified event.”

Here you see which ticket types an event already offers, each class arriving as its own bundle.

When to use it

before Create a Ticket Class, to check the tier you plan to add is not there yet, or to copy an event's ticket set into a report.

Watch out

an event with no ticket class returns zero bundles, so plan for that case before mapping the result.

Eventbrite9

Search for Events by Organization

In Make“Retrieves a list of events by the corresponding organization.”

Search for Events by Organization gathers the events that belong to one organization in Eventbrite, whether they are old or new.

When to use it

your company runs several brands as separate organizations, and one of them needs its own calendar feed or listing page.

Watch out

this search returns what already exists; to catch only events created from now on, Watch Events suits better.

Eventbrite10

Search for Events by Series

In Make“Retrieves a list of events by the corresponding series.”

If a recurring format, like a monthly meetup, is set up as a series in Eventbrite, this module fetches the events of that series.

When to use it

you want every date of a course or meetup series in one sheet, to track them side by side.

Watch out

it only sees events tied to that series. One-off events from the same organizer stay out, so use Search for Events by Organization for those.

Eventbrite11

Search for Events by Venue

In Make“Retrieves a list of events by the corresponding venue.”

This search lists what is planned at one place, which helps when several teams book the same room or hall.

When to use it

the venue manager wants a shared view of every event set in their space.

Watch out

only events attached to that venue in Eventbrite come back, so check the venue is filled in on each event.

Need help

Need help automating Eventbrite with Make?

A person reads every message.

FAQ

Eventbrite and Make: common questions

01Is the Eventbrite Make integration free?

Yes. Eventbrite is a standard app in Make, so it works on the Free plan. That plan has 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) lower the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Each module run on a bundle counts as an operation against your monthly credits. What Eventbrite itself charges is a separate matter, not covered here.

02What do you need to connect Eventbrite to Make?

An Eventbrite account that reaches the events you want to automate, plus a Make account. Make's documentation lists no other prerequisite. You add any Eventbrite module, click Create a connection, name it if you like, then either authorize Make on Eventbrite's page or paste the key Eventbrite provides, and save. That single connection serves all 17 Eventbrite modules, so you set it up once per account. If a module shows no events afterwards, check that you signed in with the account that owns them.

03Do Eventbrite triggers in Make fire instantly?

Only one does. Watch Orders is an instant trigger: Eventbrite calls Make through a webhook as soon as a new order comes in for the chosen event. The five others, Watch Attendees, Watch Attendees In Organization, Watch Events, Watch Orders by Event and the trigger that follows your own purchases as a buyer, are scheduled: Make checks Eventbrite on the scenario's schedule, every 15 minutes by default. On the Free plan the shortest gap is 15 minutes, and paid plans go down to 1 minute. If a sale must set something off at once, build on Watch Orders.

04What if an Eventbrite module you need is missing in Make?

Use Make an API Call. This module sends any request to the Eventbrite API with the connection you already have, so you are not limited to the listed modules. You write the request yourself, which means reading Eventbrite's API reference. Keep in mind that Make marks its Eventbrite documentation as limited, with no official troubleshooting section, so test each step with Run once and read the returned bundles. Before writing a request, check the searches too: List Orders or Search for Events by Venue may already return the data you were about to fetch by hand.

05Should you use Make or n8n for Eventbrite?

It depends on what your scenario needs. In Make, Eventbrite comes with 17 modules, including Watch Orders, an instant trigger for new orders, and Make an API Call for everything else. The same app also has a node in n8n. Neither tool is ranked here: list the triggers and actions your process calls for, then check that each one exists on the side you pick. The dedicated n8n page for Eventbrite and the comparison between the two tools, both linked higher on this page, give you the material to decide.

Add an Eventbrite module

Name the connection

Authorize Make and save

Create the scenario

Add Create an Event

Add Create a Ticket Class

Test with Run once

Schedule and switch on

Need help automating Eventbrite with Make?