Resources · Zapier integration

nunify Zapier integrationAutomate nunify with Zapier.

The nunify Zapier integration gives you 3 triggers, 3 actions and 0 searches. All three triggers are instant, so registrations and check-ins reach your other tools straight away, even on the free plan. Here is what each one does, what it costs and where it trips.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the nunify Zapier integration does for your events

Zapier links apps so that an event in one runs a step in another, without anyone copying data by hand. nunify is a platform for running events, virtual, hybrid or in person, from registration to check-in. Through Zapier, what happens in nunify can reach your CRM or mailing tool, and other apps can add contacts and registrants to your event.

Three results organisers build first. A CRM that knows who signed up: New Registration passes each attendee to your sales or marketing tool the moment they register. A rescue list for lost sign-ups: Abandoned Cart catches people who started registering and stopped, so someone can follow up. A live attendance log: Attendee Check-In records who actually turned up, and Get Ticket pulls the matching ticket by email.

What Zapier does not do here. There is no search step for nunify, so the only way to look up an existing ticket is the Get Ticket action, and only by the registered email. There is no update or delete action: Zapier can add people to an event, not edit or remove them. And nothing that happened before the Zap was switched on is ever replayed.

The good news is speed: all three triggers are instant, so the plan you are on does not slow them down. If you are still choosing a tool, the Make vs Zapier and n8n vs Zapier comparisons lay out the differences criterion by criterion.

Vocabulary

The Zapier words you will meet, in one minute

Eight terms come back on this page. Here they are once, in plain words.

Zap
The automation you build: 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 registration in nunify. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or fetches something for you, like adding a contact to an event.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Instant trigger
A trigger the app reports itself the moment the event happens. All three nunify triggers work this way.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. nunify has none of these.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What it really costs to run nunify through Zapier

The trigger never costs a task, so a registration or a check-in arriving in Zapier is free on its own.

  • TriggerFree, and instant on every plan
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, nunify works on the free plan
  • Filter or second actionMulti-step Zap, paid plan

You pay per action that succeeds, and a failed one is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. The interval grid below applies to polling triggers only; nunify's triggers are instant, so they fire straight away on every plan. A filter or a second action, as in the Zap further down, makes it multi-step and puts you on a paid plan. nunify is not a premium app.

Connect

Connect your nunify account to Zapier in three steps

  1. 01

    Open the connections page

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

  2. 02

    Pick nunify and sign in

    Type nunify in the dialog, select it and click Add connection. A tab opens on nunify: sign in with the account that runs the events you want to automate.

  3. 03

    Grant access and come back

    Allow Zapier to use the account. If an event is managed by a colleague, check first that your login has access to it, otherwise your Zaps will not see its registrations.

First Zap

Your first Zap: log every check-in with its ticket

GoalEach time an attendee checks in, fetch their ticket from nunify and add a line to an attendance sheet.

  1. 01

    Set the trigger

    Create a Zap, pick nunify as the app and Attendee Check-In as the event, then choose your nunify connection. The Zap will start the moment someone checks in.

  2. 02

    Test it on a real check-in

    Run the trigger test. Zapier brings back the three most recent check-ins from your account; pick one so the next steps have a real attendee and email to map.

  3. 03

    Add Get Ticket

    Add a nunify action, Get Ticket, and map the attendee's email from the trigger into Email Address. It must be the email used to register.

  4. 04

    Write the line in your sheet

    Add your spreadsheet as the last step and map the name, email and ticket details. Two actions after the trigger make this a multi-step Zap, so a paid plan.

  5. 05

    Test, then publish

    Test each step once and read what came back before going further. Then publish to switch the Zap on. Check-ins from before that moment are not logged.

Triggers

The 3 nunify triggers, one by one

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

1

Abandoned Cart

Instant trigger

In Zapier“Triggers when the cart is abandoned”

Starts your Zap when someone begins registering for your event and leaves before finishing. That half-finished sign-up is the moment to plan a follow-up, before the person forgets about the event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a conference organiser wants every unfinished sign-up sent to the sales team's CRM as a warm lead, so a colleague can call while the interest is fresh.
Watch out
carts abandoned before you published the Zap are never sent, so start it before registrations open.
2

Attendee Check-In

Instant trigger

In Zapier“Triggers when an attendee has checked in to a location or nunify event.”

Fires when an attendee checks in, whether at a physical location or into a nunify event. It is the one signal that tells you who actually showed up, not just who registered.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a trade-show team wants each badge scanned at the door to land in an attendance sheet, so the post-event email goes only to people who came.
Watch out
at the opening rush, a burst of check-ins means a burst of tasks; count them against your plan.
3

New Registration

Instant trigger

In Zapier“Triggers when an attendee registers for a nunify event.”

Reacts each time an attendee registers for one of your nunify events. The registrant's details come along, ready for your CRM, your newsletter or your team chat.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a webinar host wants every new registrant added to a mailing list straight away, so the reminder sequence starts without a manual export.
Watch out
pair it with Add Registrant on the same event only with care, or the Zap will register people in a loop.
Actions

The 3 nunify actions, grouped by what they do

nunify gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Contact

Action

In Zapier“Creates a contact in your event in nunify.”

Creates a contact inside one of your nunify events, without registering them or issuing a ticket. Think of it as putting a person on the event's books.

When to use it
speakers or sponsors collected in a form need to exist in the event without going through registration.
Watch out
when the person also needs a ticket, Add Registrant is the action to pick instead.
2

Add Registrant

Action

In Zapier“Registers an attendee to your event in nunify and issues a ticket for them.”

Registers an attendee to your nunify event and issues them a ticket in the same move. It is the action to use when registrations happen somewhere else.

When to use it
people who buy a pass through your own shop or a partner's form get their nunify ticket without retyping.
Watch out
this creates a registration, so a Zap watching New Registration will fire on it.
3

Get Ticket

Action

In Zapier“Find a ticket from Nunify by email address”

Fetches an existing ticket from nunify using the email address the attendee registered with. What it finds is handed to the steps that follow.

When to use it
a check-in or a support request carries an email, and you need the ticket details to log or answer it.
Watch out
Email Address is required, and only the registration email works.
When it breaks

When a nunify Zap breaks, and why

Zapier attaches no help article to nunify, so the known failure points are the general ones, plus the email that Get Ticket depends on.

Most broken runs come from four situations. When you cannot place a failure, the Zapier troubleshooting page walks through the checks in order.

  • Earlier registrations are never sent

    A Zap only reacts to what happens after you publish it. Registrations, carts and check-ins from before are not replayed; moving that backlog is a separate job.
  • A Zap that registers in a loop

    Use Add Registrant behind New Registration on the same event and each registration creates another, which starts the Zap again and burns your tasks.
  • Get Ticket finds nothing

    The lookup only works with the email the attendee registered with. A different or misspelt address from another tool returns no ticket.
  • A bulk import gets held back

    Importing a large guest list at once can produce a huge batch of events. Zapier's flood protection may hold those items back instead of running them.
Need help

Need help automating nunify with Zapier?

A person reads every message.

FAQ

nunify Zapier integration: the questions people ask

01Is the nunify Zapier integration free?
Yes, it works on the free plan. nunify is not a premium app on Zapier, so the 3 triggers and 3 actions are all available without paying. The free plan gives you 100 tasks a month and unlimited Zaps, with one limit that matters: each Zap has two steps, one trigger and one action. Sending a new registrant to a mailing list fits. Fetching a ticket and then logging it, or filtering registrations by event, needs a paid plan. Prices are not listed here because they change too often.
02How many tasks does a nunify Zap use?
One task per action that succeeds, and nothing for the trigger. A registration or a check-in arriving in Zapier costs nothing on its own. A Zap that adds each new registrant to a mailing list uses one task per registrant; the check-in Zap on this page, which runs Get Ticket and then writes a row, uses two per attendee. An action that fails is not counted. On a busy event day, check-ins come in waves, so estimate attendance against the 100 tasks of the free plan.
03Does nunify reach Zapier instantly?
Yes. All three nunify triggers are instant triggers: nunify tells Zapier the moment a registration, an abandoned cart or a check-in happens, and the Zap starts at once. The interval grid of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, only applies to polling triggers, so it does not slow nunify down. That type is set by nunify's own connection to Zapier and cannot be changed in the editor. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect nunify to Zapier?
A nunify account with access to the events you want to automate. You add the connection once from the Apps page of Zapier with the + Add connection button, sign in to nunify in the tab that opens, and grant access. Every Zap then reuses it. If an event is run by a colleague's account, make sure your login can reach it first. For Get Ticket, the real prerequisite is having the email the attendee registered with somewhere in your Zap.
05Why does Get Ticket return nothing?
Usually because the email it received is not the one used to register. Get Ticket looks up a ticket by email address only, and that field is required. If your CRM or form holds a work address while the attendee registered with a personal one, there is no match. Check what the earlier step actually maps into Email Address, test with an attendee you know is registered, and when the Zap starts from New Registration or Attendee Check-In, map the email those triggers carry.
06What if the nunify operation you need does not exist?
Then Zapier cannot do it with nunify today, and no setting adds it. The integration has three triggers, three actions, no search, and no way to update or delete a registration. Cancelling a ticket, changing an attendee's details or reacting to session attendance are outside what it covers. The options are to rebuild the Zap around the operations that exist, or to look at whether another automation tool offers a nunify connector with the missing step.
07Zapier, Make or n8n for nunify?
It depends on what you weigh most, not on a winner. Zapier is quick to start with: nunify works on the free plan, the triggers are instant and every operation is ready to pick. The limits are the two-step cap on the free plan and the per-task billing on busy event days. Make and n8n count and run steps differently, which can matter when each check-in feeds several tools. Compare them on attendance volume, budget and who on the team will maintain the Zaps.