Resources · Make integration

Humanitix Make integrationAutomate Humanitix with Make.

Need your Humanitix events to show up in the rest of your tools? The Humanitix Make integration gives you 3 modules: two actions and one search. This page is for event organizers new to Make, and it walks you from the API key to a first working scenario.

Try the Humanitix integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Humanitix Make integration do for you?

The Humanitix Make integration lets Make read your events and pass them to other apps, with no code. You build a scenario, the automation Make runs for you, out of modules, the bricks of that chain. Humanitix brings three of them: a search, an action that reads one event, and an open API call.

An up-to-date event list elsewhere. Put Search Events at the start of a scenario and Make brings back your events as bundles, one item per event that flows to the next module. From there, you can write each one into a sheet or a base; the Airtable Make integration shows that side.

The full picture of a single event. When a search or another app already tells you which event matters, Get an Event fetches that one event so its data can be mapped into an email, a message or a CRM record.

Anything the two modules skip. Make an API Call reaches any endpoint of the Humanitix API with the same connection, so you are not stuck when a listed module stops short.

What Make does not offer here: a trigger. Nothing in the app wakes a scenario up by itself, so you start it on a schedule set in Make or from another app. The Make documentation for Humanitix also flags itself as AI-generated and asks you to verify important information. Before choosing a plan, read our Make pricing breakdown. Humanitix often has an n8n node as well; our n8n vs Make comparison lays out both tools.

Connect

How do you connect Humanitix to Make?

  1. 01

    Copy your API key in Humanitix

    You need an active Humanitix account and its API key. Open the account settings in the Humanitix Console, go to the advanced settings, then to the API key subsection, and copy the key shown on screen. Keep it handy for the next step.

  2. 02

    Add a Humanitix module in Make

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; that field is optional. Paste the API key you copied, or follow the instructions Make shows on screen, then save. The module can now read your Humanitix account.

First scenario

Build your first scenario with Humanitix

GoalWhen the scenario runs on its schedule, Make lists your Humanitix events and reads each one with Get an Event, ready for the next module you add.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. Search for Humanitix and pick Search Events as the first module.

  2. 02

    Link your account

    Click Create a connection and paste your API key as shown above. Then fill the module fields; once the connection exists, Make lists what it can read from your account.

  3. 03

    Add Get an Event

    Click the + on the right of Search Events and choose Get an Event. Map the event coming out of the search into it, so each event found gets read in full.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open them to check that the events are the ones you expected.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module, Scheduling, and keep the default of every 15 minutes or pick another interval your plan allows. Then switch the scenario on.

Modules

What each Humanitix module does

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

Humanitix1

Get an Event

Action

In Make“Retrieves an existing event.”

You get one existing Humanitix event back as a single bundle, ready to feed its data into the next module, whether that is an email, a row or a task.

When to use it
another step already knows which event you care about, for example the output of Search Events or a record from another app.
Watch out
it reads one event only; to go through several, put a search in front of it.
Humanitix2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens up the rest of the Humanitix API: it calls any endpoint you choose, signed with the connection you already created, so no second login is needed.

When to use it
the thing you need is neither searching events nor reading one, and no other module covers it.
Watch out
you describe the request yourself, so keep the Humanitix API documentation open while you set it up.
Humanitix3

Search Events

Search

In Make“Retrieves a list of events.”

Search Events hands you a list of your Humanitix events, each one as its own bundle, so every module after it runs once per event found.

When to use it
you want to push all your events into a sheet or a base, or start a scenario that has no event in hand yet.
Watch out
a search can return zero, one or many bundles, and each module after it then counts an operation per bundle on your plan.
Need help

Need help automating Humanitix with Make?

A person reads every message.

FAQ

Humanitix and Make: common questions

01Is the Humanitix Make integration free?
Yes, Humanitix is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Every module run counts as an operation, the unit Make tracks on your plan. You also need an active Humanitix account, whose subscription options are on the Humanitix pricing page.
02What do you need to connect Humanitix to Make?
Two things: an active Humanitix account and its API key. The key sits in the Humanitix Console, under account settings, then advanced settings, then the API key subsection. In Make, add any Humanitix module, click Create a connection, optionally name it, and paste the key. That single connection then serves all three modules, Search Events, Get an Event and Make an API Call, so you only set it up once. Nothing else is listed as a requirement in the Make documentation for this app.
03Can a Humanitix scenario start by itself in Make?
Not from Humanitix, because the app has no trigger module in Make. You have two ways to start anyway. The first is a schedule: put Search Events first and set Scheduling on it, every 15 minutes by default, or as often as every minute on a paid plan. The second is to open the scenario with a module from another app, such as a form or a CRM, and use Get an Event further down. In both cases the timing depends on the schedule or on the other app, never on Humanitix itself.
04What if the Humanitix module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Humanitix API with the connection you already set up, so it covers whatever Search Events and Get an Event leave out. You write the request yourself, which means checking the Humanitix API documentation first. Keep in mind that the Make documentation for Humanitix states it was generated with AI and may contain mistakes; verify important details, and contact Humanitix directly if something in their documentation looks unclear.
05Should you pick Make or n8n for Humanitix?
It depends on the tool your team already uses. On Make, Humanitix comes with 3 modules: Search Events, Get an Event and Make an API Call, available from the Free plan. The same app often has an n8n node too, so both tools can usually reach your events. Compare which modules each side offers for what you want to do, and build where your other automations already live. That keeps connections, scenarios and troubleshooting in one place instead of spread over two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations