Resources · Make integration

Airmeet Make integrationAutomate Airmeet with Make.

Can Make take the event admin off your plate? The Airmeet Make integration gives you 10 modules: 2 instant triggers, 6 actions and 2 searches. This guide is for event and marketing teams: link your account, build a first scenario, then pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Airmeet Make integration do?

The Airmeet Make integration links your Airmeet account to Make so that registrations, guest lists, speakers and the event itself can be handled by a scenario, which is the automation you build in Make as a chain of modules. A module is one brick: a trigger that starts things, an action that does something, or a search that returns items.

A guest list that keeps itself up to date. Your invitees sit in a spreadsheet or a CRM. Each new name goes through Add an Authorized Attendee, and a cancellation goes through Remove an Authorised Attendee, so the private event matches your source list. The Airtable Make integration is a common place to keep that list.

Sign-ups that reach sales before the event. Watch New Registration for an Airmeet starts the scenario the moment someone registers, and the next module sends that person to your CRM. Want the program too? Fetch Airmeet Sessions returns every session so another tool can share the agenda.

A follow-up based on who really showed up. Watch Attendee Joined an Airmeet and Fetch Airmeet Participants hand over attendance data, ready to tag contacts in a tool such as the one covered in our Agile CRM Make integration guide.

Know the limits before you start. Attendance data only arrives once the event is over, and Make itself warns that its Airmeet documentation is AI-generated and may contain mistakes, so check anything critical with Airmeet. For an endpoint the listed modules skip, Make an API Call reuses your connection. The same app often has an n8n node as well; the n8n vs Make comparison lays out both tools side by side.

Connect

How do you connect Airmeet to Make?

  1. 01

    Generate your API key in Airmeet

    Airmeet asks for an active account and an API token. In Airmeet, open the Integrations tab, click API Access Key, then Generate access key. Copy both the API key and the API secret shown on screen.

  2. 02

    Add an Airmeet module and open the connection

    In your Make scenario, add any Airmeet module and click Create a connection. A connection is your Airmeet account linked to Make once, then reused by every Airmeet module. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Enter the key and the secret you copied, or follow the instructions Make shows on screen. Once saved, Make can read your events, so you pick an airmeet from a list instead of typing its reference.

First scenario

Your first scenario: a guest list that feeds Airmeet

GoalWhen a new guest appears in your list in another app, Make adds that person as an authorized attendee in Airmeet.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. The editor stays empty until you pick one.

  2. 02

    Start from your guest list

    Search for the app that holds your invitees, a spreadsheet or a CRM, and pick the module that watches new entries. Link that account with Create a connection.

  3. 03

    Add Add an Authorized Attendee

    Click the + on the right of the first module, search for Airmeet and choose Add an Authorized Attendee. Connect Airmeet, then choose your event from the list Make offers.

  4. 04

    Map the guest and test with Run once

    Map the guest details coming from the first module into the Airmeet fields. Click Run once and read the bundle, one item passing from module to module, that each step received.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. Scheduling is set to every 15 minutes by default, and the Free plan does not go below that. Adjust it if needed, then switch the scenario on.

Triggers

What starts an Airmeet scenario

2 modules start a scenario when something happens in Airmeet. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Airmeet as soon as it happens.

Airmeet1Watch Attendee Joined an Airmeet

Watch Attendee Joined an Airmeet

Instant trigger

In MakeTriggers when attendee joined an airmeet. All data for this trigger is sent post-event completion.

This trigger gives Make one bundle per attendee who joined your event, so real attendance can flow into a CRM or a follow-up list. Airmeet sends all of this data once the event is completed, not while sessions are running.

How it fires
instant: Airmeet calls Make through a webhook instead of Make checking on a schedule, and for this trigger the data comes after the event ends.
When to use it
post-event follow-up, when people who showed up should get a different message from those who only registered.
Watch out
nothing that must happen during the event can hang on it; build those around registrations.
Airmeet2Watch New Registration for an Airmeet

Watch New Registration for an Airmeet

Instant trigger

In MakeTriggers when new registration is added for the selected airmeet.

Each time someone registers for the airmeet you select, this trigger opens the scenario with that registration as a bundle. It is the natural entry point for anything a sign-up should set off: a new CRM record, a row in a shared sheet, a message to the team.

How it fires
instant: Airmeet calls Make through a webhook as soon as the registration is added.
When to use it
sales wants every new sign-up in the pipeline while there is still time to reach out before the event.
Watch out
the trigger follows the event picked in the module, so check that choice before switching the scenario on.
Modules

What the Airmeet modules do

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

Airmeet1

Add an Authorized Attendee

Action

In MakeAdds an authorized attendee to the airmeet.

Puts one person on the authorized attendee list of an airmeet, so nobody has to type names into Airmeet by hand. Each bundle that reaches the module adds one guest.

When to use it
invitations for a private event are managed in a CRM or spreadsheet and Airmeet should follow that list.
Watch out
it only adds; pair it with Remove an Authorised Attendee for guests who drop out.
Airmeet2

Add a Speaker

Action

In MakeAdds a speaker to the airmeet.

Registers a speaker on an airmeet straight from your scenario data, which spares you the copy and paste when the lineup is long.

When to use it
speakers confirm through a form or a shared sheet, and each confirmation should land in the event.
Watch out
every bundle is one operation, the unit Make counts on your plan, so a person sent twice is also processed twice.
Airmeet3

Create an Airmeet

Action

In MakeCreates a new airmeet.

Creates a new airmeet, the event itself in Airmeet, from data your scenario already holds. An approved request can become an event without anyone opening Airmeet.

When to use it
event requests are approved in a project tool or a form and the event shell should follow.
Watch out
each run creates one more event, so test with Run once on a single bundle.
Airmeet4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Sends the Airmeet API a request you define, using the connection you already set up. It is the way to reach what the other nine modules leave out.

When to use it
you need an Airmeet endpoint that no listed module covers.
Watch out
you describe the request yourself, which asks for more comfort with APIs than the ready modules.
Airmeet5

Manage an Airmeet

Action

In MakeStarts or ends an already created airmeet.

Starts or ends an airmeet that already exists, so a scenario can open or close the event when a signal arrives from somewhere else.

When to use it
the producer marks the event as ready or finished in a shared tool and Airmeet should follow without a second click.
Watch out
it cannot open a new event; run Create an Airmeet first.
Airmeet6

Remove an Authorised Attendee

Action

In MakeRemoves an authorized attendee from the airmeet.

Takes a person off the authorized attendee list of an airmeet, the mirror image of Add an Authorized Attendee. Access stays aligned with your source list.

When to use it
a cancellation form is submitted or a contact changes status in your CRM.
Watch out
the removal hits your real event, so run it once on a test guest before you map real contacts.
Airmeet7

Fetch Airmeet Participants

Search

In MakeFetches a list of partisipants for a selected airmeet.

Returns the participants of the airmeet you pick, one bundle per person, so the following modules can work through the whole list.

When to use it
after the event, when the full participant list should reach your CRM or a sheet in one pass.
Watch out
a search can return zero, one or many bundles, and every later module runs once per bundle, which adds operations.
Airmeet8

Fetch Airmeet Sessions

Search

In MakeFetches a list of sessions for a selected airmeet.

Lists the sessions of a selected airmeet, each one as its own bundle, ready to become an agenda somewhere else.

When to use it
the program should appear in a team channel, a newsletter tool or a shared document before doors open.
Watch out
if the program is still empty in Airmeet, the search returns zero bundles; fill it before testing with Run once.
Need help

Need help automating Airmeet with Make?

A person reads every message.

FAQ

Airmeet and Make: common questions

01Is the Airmeet Make integration free?
Yes. Airmeet is a standard Make app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes, and caps files at 5 MB and data transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. You still need an active Airmeet account with API access, and that subscription is set by Airmeet, not Make.
02What does connecting Airmeet to Make require?
An active Airmeet account and an API key. In Airmeet, the Integrations tab has an API Access Key section with a Generate access key button; copy the API key and the API secret it displays. In Make, add any Airmeet module, click Create a connection, give it a name if you like, and paste both values. For an instant trigger, click Create a webhook before Create a connection. The connection is then shared by every Airmeet module in your scenarios.
03Do the Airmeet triggers in Make fire in real time?
Partly. Both Airmeet triggers are instant: Airmeet calls Make through a webhook instead of waiting for a schedule. Watch New Registration for an Airmeet fires as soon as a registration is added. Watch Attendee Joined an Airmeet is different: Airmeet sends its data once the event is completed, so it suits follow-up work, not actions during the event. Scenarios that start from another app keep the usual schedule, every 15 minutes by default.
04What if an Airmeet module is missing in Make?
Use Make an API Call. It sends any request to the Airmeet API with the same connection, which covers the endpoints the nine other modules do not touch. You write the request yourself, so it takes more care than a ready module. Also keep in mind that Make labels its Airmeet documentation as AI-generated and possibly inaccurate; when a field or behavior matters, confirm it with Airmeet directly before building on it.
05Should you use Make or n8n for Airmeet?
It depends on the tool your team already works in. On Make, Airmeet comes with 10 ready modules, including 2 instant triggers and Make an API Call for the rest, and every step is set up in the visual editor. Many apps also have an n8n node, so check whether Airmeet is covered there before deciding. Neither tool is ranked here: compare the modules each one offers for your case, then build where your other automations already live.