Resources · Make integration

Eventzilla Make integrationAutomate Eventzilla with Make.

What if every new registration and ticket sale in Eventzilla reached the rest of your tools on its own? The Eventzilla Make integration gives you 7 modules: 3 triggers and 4 actions. This guide is for event organizers and ops teams; it walks you through the connection and a first working scenario.

Try the Eventzilla integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Eventzilla Make integration do for you?

The Eventzilla Make integration links your Eventzilla account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or writes data. Once connected, new attendees, tickets and transactions flow into your other apps, and check-ins can be written back to Eventzilla without anyone typing them.

Door check-ins recorded for you. When a badge scan or a form in another tool confirms that someone arrived, the Create a Checkin module marks that attendee as present in Eventzilla, and Create a Checkout records when they leave. Your attendance numbers stay accurate without a volunteer updating a spreadsheet.

Sales that land in your finance tools. Watch Transactions picks up each new transaction, and Get a Transaction pulls the full record of a given one, so you can push the details to a sheet or an accounting app for the people who reconcile payments.

A guest list your whole team can see. Watch Attendees and Watch Tickets feed a shared base or a CRM with every new registration. Our Airtable Make integration guide shows the other half of that flow.

What the integration does not do: its three triggers are all scheduled, so Make checks Eventzilla on the scenario's schedule rather than being alerted at once. When a listed module is missing, Make an API Call reaches any endpoint of the Eventzilla API with the same connection. Eventzilla may also have an n8n node; the n8n vs Make comparison helps you pick, and Make training gets you started if Make is new to you.

Connect

How do you connect Eventzilla to Make?

  1. 01

    Generate your API key in Eventzilla

    In your Eventzilla account, open Settings, then App Management, and click Generate to create a new application. Copy the API key shown on screen: it is what lets Make read and write your event data.

  2. 02

    Add an Eventzilla module in Make

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

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like (it is optional), paste the API key you copied, then confirm. Make now lists the data it can read from your account.

First scenario

Your first scenario: check attendees in from another tool

GoalWhen another app confirms that a guest arrived, Make creates the matching check-in in Eventzilla.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the app where arrivals are recorded, such as a form or a sheet your door staff fills in.

  2. 02

    Add Create a Checkin

    Click the + on the right of that first module, search for Eventzilla and pick Create a Checkin. Select the connection you created earlier, or click Create a connection.

  3. 03

    Map the attendee

    Fill the module fields by mapping the attendee data coming from the first module. Each arrival travels as a bundle, one item passed from a module to the next, so each guest gets their own check-in.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time, then read the bundles each module received. Test with one guest first: the check-in lands in your real event.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

What can start an Eventzilla scenario?

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

Eventzilla1Watch Attendees

Watch Attendees

Scheduled trigger

In Make“Triggers when an attendees is created.”

Watch Attendees hands your scenario each person who registers for your events, one bundle per attendee, so the guest list can live in the tools your team already uses.

How it fires
scheduled, Make checks Eventzilla on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
you want every registrant added to your CRM or a shared base as soon as the next check runs.
Watch out
one attendee is one bundle, and every module after the trigger spends an operation per bundle, so a busy launch weighs on your plan.
Eventzilla2Watch Tickets

Watch Tickets

Scheduled trigger

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

Watch Tickets tells your scenario about every new ticket created in Eventzilla, which is the angle you want when you think in ticket types rather than in people.

How it fires
scheduled, Make looks at Eventzilla on the scenario's schedule instead of being called by it, so a new ticket shows up at the next check.
When to use it
each new ticket should trigger a note to the person who manages seating or merchandise for that event, at the next check.
Watch out
pick Watch Attendees if your follow-up is about the registrant themselves; the two triggers answer different questions.
Eventzilla3Watch Transactions

Watch Transactions

Scheduled trigger

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

Watch Transactions gives your scenario each new transaction recorded in Eventzilla, the money side of your event, so payments can reach the people and tools that track revenue.

How it fires
scheduled, Make queries Eventzilla on the scenario's schedule; on paid plans the interval can go down to 1 minute.
When to use it
your finance team logs each sale in a sheet or an accounting app and wants those rows filled without copying anything.
Watch out
test with Run once before switching on, and read the bundle to see which transaction details you can map.
Modules

What can Make do in Eventzilla?

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

Eventzilla1

Create a Checkin

Action

In Make“Creates check-in for attendees.”

Create a Checkin marks an attendee as arrived in Eventzilla, so your attendance record fills itself from whatever tool sees guests at the door.

When to use it
a badge scan, a form or a row in a sheet confirms an arrival, and you want Eventzilla to know too.
Watch out
this action writes to your live event; test with a single guest through Run once before you switch it on.
Eventzilla2

Create a Checkout

Action

In Make“Creates a Checkout.”

Create a Checkout records that a guest left, which gives you a full picture of who stayed until the end of a session or a day.

When to use it
your venue scans people on the way out, and you want the exit logged in Eventzilla alongside the check-in.
Watch out
pair it with Create a Checkin in the same event, since a checkout logically follows an arrival.
Eventzilla3

Get a Transaction

Action

In Make“Retrieve a specific information about transaction.”

Get a Transaction fetches the details of one specific transaction, so a later module can use the full record instead of the few fields you already hold.

When to use it
a refund request or a support ticket mentions a transaction, and you need its details to answer.
Watch out
it reads one transaction at a time; to follow every new sale, start from Watch Transactions instead.
Eventzilla4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Eventzilla API with the connection you already set up, which covers what the six other modules leave out.

When to use it
you need an Eventzilla feature that no listed module offers, and you are comfortable reading the API documentation.
Watch out
you write the request yourself, so try it with Run once and read the response before relying on it.
Need help

Need help automating Eventzilla with Make?

A person reads every message.

FAQ

Eventzilla and Make: common questions

01Is the Eventzilla Make integration free?
Yes, on the Make side. Eventzilla is a standard app, available from the Free plan. That plan allows 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 and remove the cap on active scenarios. Usage is counted in operations each month. You still need an active Eventzilla account, whose subscription is set by Eventzilla.
02What do you need to connect Eventzilla to Make?
An active Eventzilla account and an API key. In Eventzilla, go to Settings, then App Management, click Generate to create a new application, and copy the key shown on screen. In Make, add any Eventzilla module, click Create a connection, optionally name it, and paste the key. That connection is then reused by every Eventzilla module in your scenarios, so you only do this once per account, and every new module you add later picks it up from a list.
03Do Eventzilla triggers in Make fire instantly?
No. Watch Attendees, Watch Tickets and Watch Transactions are all scheduled triggers: Make checks Eventzilla on the scenario's schedule rather than being alerted the moment something happens. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two runs; paid plans go down to 1 minute. If you need a faster reaction, a paid plan with a short interval is the lever the integration offers.
04What if the Eventzilla module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Eventzilla API with the same connection as the other modules, so you do not need a separate login. The listed modules cover attendees, tickets, transactions, check-ins and checkouts; anything else goes through that module. Expect to read the Eventzilla API documentation to write the request, and test it with Run once before you switch the scenario on, since the call acts on your live Eventzilla data.
05Should you use Make or n8n for Eventzilla?
It depends on the tool your team already builds in. Make offers Eventzilla as a native app with 7 modules: 3 scheduled triggers and 4 actions, including Make an API Call for the rest of the API. Eventzilla may also have an n8n node, so check its coverage for the objects you care about. Compare the two on the modules you actually need for your event flow, and on which editor your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations