Humanitix Salesforce Integration: Options for NZ Event Organisers and Nonprofits

If you sell tickets on Humanitix and run your organisation on Salesforce, there are four realistic ways to connect them: the official managed package built by AlphaSys, a Zapier or Make automation, a custom build on the public API, or the unlocked package we built at SaaSKool. Which one fits depends on how much control you need over where the data lands.

Why Ticket Buyers Belong in Your CRM

Every attendee list is a relationship list. For a nonprofit, tonight's ticket buyer is next year's donor; for a training business, this workshop's attendee is the next course's repeat customer. If ticketing data stays inside the ticketing platform, none of that shows up when your team looks at a contact in Salesforce, and questions like "which events has this supporter actually come to?" get answered from memory or not at all.

Campaigns are the other half of the case. When each event exists in Salesforce with its attendees attached, you can report on what each event contributed to fundraising, membership or sales, and stop treating events as a cost centre that ends when the chairs are stacked.

What Humanitix Is (and Why NZ Organisations Like It)

Humanitix is a ticketing platform with an unusual model: it is structured as a charity, and it states that 100% of its booking fee profits fund social impact. Its running donation counter showed more than $22.7 million donated as at July 2026. In New Zealand it operates through the Humanitix New Zealand Charitable Trust, and you will find it behind community events, conferences and fundraisers across Auckland, Wellington, Christchurch and beyond. That model makes it a natural fit for the nonprofits and community organisations we work with, which is exactly the crowd most likely to also run Salesforce; if that is you, our NZ nonprofit Salesforce guide is the companion read.

The Four Ways to Connect Humanitix and Salesforce

Option	Cost signal (as at July 2026)	Best for
Official managed package (by AlphaSys)	See Humanitix for current terms	Standard one-way sync into a straightforward org
Zapier	Free tier (100 tasks/mo) · paid from US$19.99/mo billed annually	Event-driven automations, quick start
Make	Free tier (1,000 credits/mo) · Core from US$9/mo	Same jobs, more technical, cheaper
Custom build on the public API	Your development time	Fully bespoke mapping and logic
SaaSKool's unlocked package	Talk to us	Custom mapping with a packaged head start

Sources: Humanitix help centre, Zapier pricing, Make pricing.

The Official Managed Package

Humanitix's own integration is a Salesforce managed package built by Salesforce partner AlphaSys, documented in the Humanitix help centre. It is a one-way sync from Humanitix into Salesforce covering events, orders, tickets, ticket types, dates and the answers to your checkout questions, with buyer details synced as contacts and each event created as a Salesforce campaign. Matching runs on email address first, with name and mobile as secondary matchers.

Know the boundaries before you rely on it. It does not sync email campaigns, tours, gift cards, access codes, host profiles or, notably, addresses. Only events owned by the connecting Humanitix account sync, so shared events stay behind. Contacts arrive as contacts, never leads, and the connected Salesforce user needs marketing user access to create campaigns. If a clean, standard, one-way feed into standard objects is all you need, this is the purpose-built option and the sensible default.

Zapier and Make: Event-Driven Automations

Zapier's Humanitix connector has the triggers that matter: new order, new attendee, new event, new contact, and the quietly excellent new attendee check-in. That last one enables the play most organisations miss: a same-week thank-you or follow-up task in Salesforce for people who actually walked in the door, not just those who bought a ticket. Make's Humanitix modules are thinner (get an event, plus arbitrary authenticated API calls) but its Salesforce side is deep, and it is the cheaper platform.

The structural limits are the usual ones: record-at-a-time flows, no historical backfill, and your mapping logic lives inside the automation tool rather than inside Salesforce.

The Public API: Fully Custom

Humanitix publishes a read-only public API covering events, orders, tickets and tags. Authentication is an API key from your account's advanced settings, the rate limit is 200 requests a minute, and Humanitix commits to six months' notice for breaking changes, all as at July 2026. Read-only matters for the architecture: your integration pulls from Humanitix and writes into Salesforce, so the sync logic, scheduling and error handling live on your side.

This is the route when the packaged options cannot express your model. The cost is that someone has to design, build and maintain it.

The Unlocked Package We Built

We kept meeting the same gap: organisations that wanted Humanitix data in Salesforce, but mapped to how their org actually works, especially nonprofits running NPSP or Nonprofit Cloud data models rather than plain standard objects. A managed package cannot be reshaped, because its internals belong to the vendor. So we built our own connector as an unlocked package.

Unlocked is a Salesforce packaging format, and the difference is ownership: the components deploy into your org where your admin or partner can inspect and adapt them, rather than sitting behind a vendor's lock. In practice that means the mapping, matching and automation around your Humanitix data can be tailored to your org and extended later, without waiting on anyone's product roadmap. If you are weighing Nonprofit Cloud against NPSP, or your event data needs to feed existing dashboards and duplicate rules, that control is the whole point.

We would rather show you than pitch you: get in touch for a walkthrough of what the package syncs and whether it fits your org, and we will tell you honestly if the official package or a NZ$20 Zapier flow serves you better.

When Not to Integrate (Yet)

• You run one or two events a year and no follow-up programme. A spreadsheet export after each event may genuinely be enough. Integrate when follow-up becomes someone's actual job.
• Your Salesforce data needs a cleanup first. Attendee syncs multiply whatever duplicates you already have. Do the data hygiene work first; every option above gets better afterwards.
• Nobody has agreed what happens after the sync. Data arriving is not a strategy. Decide the plays (post-event thanks, donor asks, next-event invitations) before wiring anything.

How We'd Choose

• Standard org, standard objects, one-way feed is fine: the official managed package. It exists for exactly this.
• One specific automation, this week: Zapier, especially for check-in-driven follow-up.
• NPSP or Nonprofit Cloud, custom matching rules, your own reporting model: an unlocked build; that is why ours exists.
• Unusual requirements and in-house developers: the public API, designed properly.

Frequently Asked Questions

Does Humanitix integrate with Salesforce? Yes. Humanitix offers an official Salesforce integration, a managed package built by Salesforce partner AlphaSys, which syncs events, orders, tickets and contacts one way from Humanitix into Salesforce. Zapier and Make connectors and a read-only public API are also available. SaaSKool separately maintains an unlocked package for organisations that need a more customised sync.

What does the official Humanitix Salesforce package sync? As at July 2026: events, orders, tickets, ticket types, dates, checkout questions (as order and ticket attributes) and buyer contact details, with each Humanitix event created as a campaign in Salesforce. Buyers sync as contacts, not leads. It does not sync email campaigns, tours, gift cards, access codes, host profiles or addresses.

Is the Humanitix Salesforce integration two-way? No. The official integration is one-way: data flows from Humanitix into Salesforce, and changes you make in Salesforce are not written back to Humanitix. For most organisations that is the right shape, because Humanitix owns the ticketing record and Salesforce owns the relationship record.

Can I build a custom Humanitix Salesforce integration? Yes. Humanitix publishes a read-only public API covering events, orders, tickets and tags, authenticated with an API key from your account settings and rate-limited to 200 requests a minute, with six months' notice of breaking changes. A custom build makes sense when you need Humanitix data mapped into your own Salesforce structures.

What is an unlocked package, and why did SaaSKool build one for Humanitix? An unlocked package is a Salesforce deployment format where the components are visible in your org and your team can adapt them, unlike a managed package whose internals the vendor controls. We built ours so organisations can shape how Humanitix data lands in Salesforce, including nonprofit data models, and keep ownership of the result.

---

SaaSKool builds Salesforce integrations for NZ and AU organisations, including our unlocked Humanitix package for nonprofits and event organisers. Want to see it against your own org? Start with the free health check or book a walkthrough.