Humanitix Zapier integrationAutomate Humanitix with Zapier.
The Humanitix Zapier integration gives you 6 triggers, 0 actions and 1 search. Every trigger is instant: an order, an attendee, a check-in or a new event reaches Zapier as it happens, even on the free plan. The search finds one of your current events.
Verified Trustpilot reviews · AI, automation & growth agency
What the Humanitix Zapier integration gives you
Humanitix is a ticketing platform that gives all of its profits to charity. Hooked up to Zapier, it becomes the starting point of your event admin: each sale, each attendee, each check-in and each new event can set off work in your other tools without anyone exporting a list.
Three results cover most needs. A buyer list that stays current: New Order and New Contact fire on every order, the first with the high-level order details, the second with all the ticket information. A guest list down to each person: New Attendee fires once per attendee, so a group booking of four gives you four runs. A door that reports back: New Attendee Check-In tells you who actually showed up.
Now for the hard limits. Humanitix offers no action on Zapier, so a Zap cannot create an event, issue a ticket or check someone in. It only listens and looks things up, through Search Events. Anything that changes data in Humanitix stays a job you do in Humanitix itself, by hand.
Comparing platforms? The same app has a Humanitix Make integration page, and our Zapier review helps you judge the tool. Operations below were read on the Zapier app page on 2026-10-01, version HumanitixCLIAPI@2.2.0.
Zapier words in one minute
Eight terms come back on this page. Here is what each one means, plainly.
- Zap
- The automation you build on Zapier: one trigger, then one or more steps that run every time that event happens.
- Trigger
- The event that starts the Zap, such as a new Humanitix order. Once the Zap is switched on, Zapier waits for it.
- Action
- What a Zap does after it starts: the step that writes, sends or moves something. Humanitix itself offers none.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Instant vs polling
- An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists, here a Humanitix event, so later steps can use what it found.
- Connection
- Your Humanitix account linked to Zapier once, then reused by every step that touches Humanitix.
What a Humanitix Zap costs you
Humanitix is not a premium app, so it runs on the free plan. Zapier bills tasks, and tasks come from completed actions.
- Free plan100 tasks a month, unlimited Zaps
- Steps on the free planOne trigger and one action
- Humanitix triggersInstant on every plan
- Premium appNo
The trigger never costs anything, and neither does Zapier waiting for an order. Each action that succeeds counts as one task; a failed one is not counted. The free plan stops at two steps, one trigger and one action. A filter or a search makes the Zap multi-step, which needs a paid plan; the two-card Zap at the top of this page fits the free plan. Speed is not an issue: all six Humanitix triggers are instant, and the polling grid below never applies to them.
Connect Humanitix to Zapier in three steps
- 01
Open your Zapier apps
In your Zapier account, open the Apps page and click + Add connection. You need a Humanitix account, plus access to any event you do not own yourself but want the Zap to follow.
- 02
Pick Humanitix
Search for Humanitix in the dialog, select it and click Add connection. A new tab opens on the Humanitix side so you can sign in with the account that runs your events.
- 03
Sign in and allow access
Log in to Humanitix and grant Zapier access. From then on, every Zap that uses Humanitix reuses this one connection, so you never repeat the sign-in for a new Zap.
Your first Zap: log check-ins in a spreadsheet
GoalEach time someone is checked in at the door, the Zap carries on only for the check-ins you care about and adds a row to a spreadsheet, live during the event.
- 01
Build: set the trigger
Create a Zap, pick Humanitix as the app and New Attendee Check-In as the event, then select the Humanitix connection you created earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent check-ins from your account, so you work on a real one. If none come back, check someone in on a test event first.
- 03
Add the filter
Click the plus icon and add Filter. Pick a field from the test, a rule of the right type and a value. The filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the step that records it
Humanitix has no action, so this step belongs to another app: pick your spreadsheet and its event for adding a row, then map the check-in values the test brought back into its columns.
- 05
Test, then publish
Test the step and check the new row. Then click Publish to switch the Zap on. Check-ins made before that moment are not picked up.
The 6 Humanitix triggers
6 events start a Zap when something happens in Humanitix, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
New Attendee
Instant triggerIn Zapier“Triggers on every attendee created on an order. Use this trigger if you want to collect customer information on the ticket level.”
Fires once for every attendee created on an order. Where an order trigger sees one purchase, this one sees each ticket holder, which is what you want for name badges or per-person follow-up.
New Attendee Check-In
Instant triggerIn Zapier“Triggers when a attendee is checked into your event”
Runs when an attendee is checked in at your event. It turns the door scan into a signal the rest of your tools can act on, while the event is still going.
New Event Drafted
Instant triggerIn Zapier“Triggers when a new event draft is created under your account. Note: the draft typically contains very little information at this point. Use "New Event Published" for fully populated event data.”
Fires as soon as a new event draft is created under your account. It is the earliest signal that something is being planned, long before tickets go on sale.
New Event Published
Instant triggerIn Zapier“Triggers when an event under your account is published for the first time.”
Fires when one of your events is published for the first time. By then the event is filled in, which makes this the trigger to announce or log an event properly.
New Order
Instant triggerIn Zapier“Triggers when a new order is made in one of your events. This includes just the high level order information”
Starts the Zap when a new order is placed on one of your events. It carries the high-level order information only, which is enough to log a sale without the ticket detail.
New Contact
Instant triggerIn Zapier“Triggers on every order made on your event. Contains all the ticket information from the order”
Fires on every order made on your event, with all the ticket information from that order. Despite the name, it is order-based, so it suits anything that needs the full detail of a purchase.
The Humanitix search
1 search step looks for data that already exists in Humanitix, so a later step can use it.
A search step looks up something that already exists so the next steps can use it. In the editor, searches sit at the bottom of the action-event list under their own heading. Three settings decide what happens when the result is not exactly one event.
Search Events
SearchIn Zapier“Search for any of your current events.”
Looks up one of your current Humanitix events and hands its details to the steps that follow. It is how a Zap started by an order or a check-in gets the context of the event itself.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create on apps that support it. Humanitix offers no find-or-create, so Search Events only ever finds.
- If multiple search results are found?Three ways out when several events match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When a Humanitix Zap breaks
Zapier ties no help article to Humanitix, so the known failure points are the ones every Zap shares, plus the overlap between its order triggers.
Most of these stay invisible until your sales go live. Four cases to keep in mind:
Sales before publishing are lost
A Zap only reacts to what happens after you switch it on. Orders and attendees from before that moment are not picked up, and moving them is a separate job.On-sale rush held back
When a trigger suddenly returns a huge batch, Zapier's flood protection can hold the runs back. A big release of tickets can produce that kind of batch.Each purchase handled twice
New Order and New Contact both fire on every order. Two Zaps doing the same job on each of them process every purchase twice and bill both.A search that finds nothing
With the default setting, a Search Events step that finds no event stops the Zap there, and the steps after it never run.
Need help automating Humanitix with Zapier?
A person reads every message.
