Resources · Zapier integration

NextEvent Zapier integrationAutomate NextEvent with Zapier.

The NextEvent Zapier integration gives you 6 triggers and 0 actions. All six are instant and cover orders, cancellations, events, invoices and seat availability. NextEvent works on the free plan; whatever the Zap does next happens in your other apps.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the NextEvent Zapier integration does for you

NextEvent is an event management platform: you sell tickets, build seating plans and check visitors in with a mobile app. Its Zapier integration only listens. When an order arrives, an event changes, an invoice moves or seats run low, it starts a Zap that carries the news to your other tools.

An early warning before you sell out. Availability Falls Below Specific Level starts a Zap when a category drops under the level you set, so you hear about it while there is still room to react.

Every order in your books. New Order, and New Order Items when you need the detail line by line, can feed a sheet, an accounting tool or a mailing list without exports.

Money and changes followed closely. Invoice Status Changes, Cancelled Order and Event Changes tell the rest of your stack when a payment status moves, an order is cancelled or an event is created or edited.

What Zapier does not do with NextEvent: there is no action and no search step. A Zap cannot create an event, issue a ticket or look up an order in NextEvent; it reacts to what happens there and passes it on. Anything that happened before the Zap is switched on is not picked up. If you are comparing tools, see our n8n vs Zapier comparison and our Zapier review.

Vocabulary

Zapier words used on this page

Seven terms in plain words. The page uses them afterward without explaining them again.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new order in NextEvent. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or creates something in another app for you.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance of your plan counts those.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when the data that arrived meets your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns it into one, and it then needs a paid plan.
Cost

What NextEvent on Zapier really costs

Zapier does not reserve NextEvent for paid plans: it works from the free plan. You pay in tasks, and none of the six NextEvent triggers costs one.

  • Reserved for paid plansNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • NextEvent triggersCost no task
  • Failed actionNot counted

Since NextEvent only brings triggers, every task is spent by the actions of your other apps. Each action that succeeds counts once, so an order copied to a sheet and announced in chat costs two tasks. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below applies to polling triggers; all six NextEvent triggers are instant, so it does not apply to them.

Connect

Connect your NextEvent account to Zapier

  1. 01

    Open Apps

    In your Zapier account, go to Apps and click + Add connection. A connection is your NextEvent account linked to Zapier once, then reused by every Zap that listens to NextEvent.

  2. 02

    Select NextEvent

    Search NextEvent in the dialog, pick it and click Add connection. You need an account on NextEvent, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and grant access

    NextEvent opens in a new tab. Sign in with the account Zapier should use and grant Zapier access. The connection can then be chosen in the trigger step of any Zap.

First Zap

Your first Zap: every NextEvent order in a sheet

GoalEach new NextEvent order adds a row to your spreadsheet, and a second action can send an email about it.

  1. 01

    Start on New Order

    Create a Zap, pick NextEvent as the trigger app and New Order as the event, then choose the NextEvent connection you added.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent orders of the connected account, so you see what an order carries and map the next step on a real one.

  3. 03

    Add the spreadsheet row

    Add your spreadsheet as the action, pick its create-row event and map the order details from the test into the columns. Test the action and check the new row.

  4. 04

    Decide on the email

    The email card is a second action: it makes the Zap multi-step, which needs a paid plan. On the free plan, keep only the spreadsheet row.

  5. 05

    Publish

    Publish the Zap to switch it on. Only orders placed after that start it; older orders stay where they are. For guided practice, see our Zapier training.

Triggers

NextEvent triggers on Zapier

6 events start a Zap when something happens in NextEvent, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Availability Falls Below Specific Level

Instant trigger

In Zapier“Triggers when a categories availability falls below a certain level.”

Watches the availability of a ticket category and starts your Zap once it falls below the level you defined.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when you want a heads-up as a category runs low, while there is still time to react.
Watch out
the Type field is required: it is the unit you define the warning level on. Pick it carefully and test the trigger to see what NextEvent sends when the threshold is crossed.
2

Event Changes

Instant trigger

In Zapier“Triggers when an event has been created or changed.”

Reacts when an event is created or changed in NextEvent, which keeps calendars, sites and teams in step with your programme.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a new date or an edit to an event has to reach a shared calendar, a website or your team chat.
Watch out
the Event field is required. It is where you select the event action that decides when this Zap runs, so choose it before you test.
3

Invoice Status Changes

Instant trigger

In Zapier“Triggers when an invoice status changes.”

Fires when the status of an invoice changes in NextEvent, and hands that invoice to the next step of your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your accounting tool needs to know that an invoice moved, without logging into NextEvent.
Watch out
a Type is required here, the invoice action that decides when the Zap runs. Test the trigger to see which invoice details come through before mapping them.
4

Cancelled Order

Instant trigger

In Zapier“Triggers when an order has been cancelled.”

Starts a Zap when an order is cancelled, so the cancellation does not stay hidden inside NextEvent.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a cancellation should update your order sheet, warn the team or take a buyer off a mailing list.
Watch out
only cancellations made after the Zap is published are picked up. If the Zap writes back to a place NextEvent watches, keep the general loop precaution in mind and test with a real cancellation.
5

New Order

Instant trigger

In Zapier“Triggers when a new order has been created.”

Runs your Zap when a new order is created in NextEvent, and passes that order to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when every sale should reach your books, your CRM or a thank-you email without anyone copying it over.
Watch out
a large batch of orders arriving at once, after an import for instance, can be held back by Zapier's flood protection. Test with a recent order to see the fields you get.
6

New Order Items

Instant trigger

In Zapier“Triggers when order has been created and processes each order item.”

Also starts when an order is created, but goes on to process each item of that order rather than the order alone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your sheet or your reporting has to follow what was bought, item by item, rather than the order total.
Watch out
check at test how the items of an order come through before you map them, and compare with what New Order returns for the same order.
When it breaks

When a NextEvent Zap breaks

Zapier attaches no help article to NextEvent, so the cases below are the general limits that apply to any Zap built on its triggers.

Go through them before you publish. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.

  • Past orders are never picked up

    A Zap only reacts to what happens after it is switched on. Orders, invoices and events that already existed are not picked up; moving them is a separate job.

  • A Zap that sets itself off

    As a general precaution: a Zap that writes into the place its own trigger watches can start itself again and again and burn through your tasks.

  • A rush of orders at once

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the run back.

  • A required choice left empty

    Three triggers need a choice first: a Type for availability, an Event action for event changes, a Type for invoice status. Set it and test before publishing.
Need help

Need help automating NextEvent with Zapier?

A person reads every message.

FAQ

NextEvent Zapier integration: common questions

01Is the NextEvent Zapier integration free?
Yes. Zapier does not reserve NextEvent for paid plans, so you can start on the free plan. It gives 100 tasks a month and as many Zaps as you like, as long as each one has two steps: one trigger and one action. A Zap that copies every new order into a spreadsheet fits that limit. Add a filter or a second action, such as an email after the row, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a NextEvent Zap use?
The NextEvent triggers use none. Tasks come from the actions in your other apps: one task for each action that succeeds. An order copied to a sheet costs one task; the same order copied and emailed costs two. An action that fails is not counted against your plan. Waiting for orders, invoices or availability alerts costs nothing either. Busy sales periods can use up the 100 tasks of the free plan quickly, so watch the count.
03Do NextEvent triggers fire in real time?
Yes, all six. Availability Falls Below Specific Level, Event Changes, Invoice Status Changes, Cancelled Order, New Order and New Order Items are instant triggers: NextEvent tells Zapier the moment the event happens, and the Zap starts right away, whatever your plan. The polling interval of the plans does not apply to them. In the editor, a Zap built on an instant trigger shows a lightning bolt. A sudden huge batch, after an import for example, can still be held back by Zapier's flood protection.
04What does it take to connect NextEvent to Zapier?
An account on NextEvent, plus read or write access on anything you do not own yourself and want the Zap to touch. From the Apps page of your Zapier account, click + Add connection, search for NextEvent, click Add connection, sign in to NextEvent in the tab that opens and grant Zapier access. The connection is then reused by every NextEvent trigger in every Zap you build, so you only do this once.
05New Order or New Order Items: which NextEvent trigger to pick?
Both start when an order is created. New Order reports the order itself; New Order Items goes on to process each item of that order. That is all the official descriptions say, so let the test decide: run each one on a recent order and read what comes back. If what you need is the order, New Order is the plainer choice; if you need the items it contains, look at what New Order Items returns. Whichever you pick, tasks are counted on the actions that follow, one per successful action.
06What if the NextEvent operation you want is not on Zapier?
Then this integration cannot do it today. Open the NextEvent page on Zapier: it shows the current list of triggers and actions, and that list is the reference. On this page there are six triggers and no action or search, so a Zap cannot create an event, issue a ticket or look up an order inside NextEvent. Anything that has to be written into NextEvent is outside what this integration covers today.
07Zapier, Make or n8n for NextEvent?
Choose on criteria, not on a ranking. On Zapier, NextEvent brings six instant triggers and no action, and a two-step Zap from an order to a sheet runs on the free plan with 100 tasks a month. Three questions settle it: how many steps your flow needs after the trigger, since filters and extra actions require a paid plan on Zapier; how many orders a month you expect, since each successful action is billed; and whether listening is enough or you also need to write into NextEvent. Ask Make and n8n the same.
Same platform

Other docs you might need on this stack.

Browse all integrations