Resources · Make integration

AirMenu Make integrationAutomate AirMenu with Make.

Can Make pick up your AirMenu orders and act on them without you? The AirMenu Make integration gives you 6 modules: 2 triggers and 4 actions. This page walks you through the connection, a first scenario and what each module is for.

Try the AirMenu integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AirMenu Make integration do for you?

The AirMenu Make integration links your AirMenu account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches for something or does something. With it, AirMenu orders and flags can start work in your other apps, and those apps can push orders or promotions back into AirMenu.

Send every new order somewhere useful. Watch New Order hands each order to the next module, so a spreadsheet, a chat tool or your accounting app can receive it without anyone copying it by hand.

Start a promotion from an outside event. Trigger a Promotion can sit at the end of a scenario that begins in another app, such as a form or a CRM. Watch Activated Flag works the other way around: it lets something happen elsewhere when a flag goes live in AirMenu.

Log orders that come from another channel. Create a New Order writes an order into AirMenu from data another module received.

A word of caution before you build. The AirMenu documentation in Make is short and marked as AI-generated, and it gives no description for any module, so the fields you see inside each module are your real guide. When a module is missing, Make an API Call reaches the AirMenu API with the same connection. If you are weighing tools, the n8n vs Make comparison sets them side by side, the Make pricing page explains plans, and Make training helps if you are new to scenarios.

Connect

How do you connect AirMenu to Make?

  1. 01

    Get your AirMenu access ready

    You need an active AirMenu account and an API key before you open Make. If you have no account yet, sign up on AirMenu first; their pricing page covers subscriptions. Keep the key at hand, you paste it in step three.

  2. 02

    Add an AirMenu module in Make

    In your scenario, add any AirMenu module and click Create a connection. A connection is your AirMenu account linked to Make once, then reused by every AirMenu module. The Connection name field is optional; a clear name helps if you run several accounts.

  3. 03

    Enter your credentials and save

    Paste the credentials you copied from your AirMenu account, or follow the instructions Make shows on screen. Once saved, the connection appears in the module and Make can list what it reads from AirMenu.

First scenario

Your first scenario: turn web form orders into AirMenu orders

GoalWhen a customer sends an order through another app, such as a web form, Make creates it in AirMenu.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. The first module decides when the whole scenario starts; here it belongs to the app that collects the order.

  2. 02

    Add the source app

    Search for the app that receives your orders, such as your form tool, pick its trigger and connect your account. Fill its fields; Make lists what it can read once connected.

  3. 03

    Add Create a New Order

    Click the + on the right of the first module, search for AirMenu, choose Create a New Order and link your account with Create a connection.

  4. 04

    Map the order data

    Fill the AirMenu fields by picking data from the first module. Each value you map comes from the order your customer sent.

  5. 05

    Test with Run once

    Click Run once with a test order. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passing between modules, here one order.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; adjust it within your plan, then switch the scenario on.

Triggers

What can start an AirMenu scenario?

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

AirMenu1Watch Activated Flag

Watch Activated Flag

triggerIn the docs only

This trigger gives your scenario a starting signal each time Make finds a flag switched on in your AirMenu account. The documentation says nothing more about flags, so open the module to see what it lets you pick.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, not the second a flag changes.
When to use it
when a flag in AirMenu should lead to work somewhere else, like a message to your team.
Watch out
the module type comes from its name in the documentation; confirm its behavior with Run once before you rely on it.
AirMenu2Watch New Order

Watch New Order

triggerIn the docs only

Watch New Order turns every fresh AirMenu order into a bundle your scenario can use, which is the simplest way to get order data out of AirMenu and into another tool.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects the orders that arrived since the previous check.
When to use it
when orders need to reach a sheet, a kitchen display app or your bookkeeping without retyping.
Watch out
each order that comes through uses operations on your Make plan, one per module that handles it, so test with Run once first.
Modules

What can Make do in AirMenu?

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

AirMenu1

Activate a Flag

ActionIn the docs only

With this action, Make switches a flag on in AirMenu for you, at the moment the rest of your scenario decides it. The documentation stops at the module name, so the fields tell you which flags are available.

When to use it
when an event in another app, such as a form answer, should change something in AirMenu.
Watch out
pair it with Watch Activated Flag carefully, or the scenario can end up reacting to its own change.
AirMenu2

Create a New Order

ActionIn the docs only

You get a real order in AirMenu without typing it, built from data that reached Make through an earlier module.

When to use it
when orders arrive through a channel AirMenu does not see, like a web form or a spreadsheet row, and belong with the rest.
Watch out
run the scenario once with test data and check the result in AirMenu, since a created order is real data in your account.
AirMenu3

Make an API Call

ActionIn the docs only

This module fills the gaps: it lets your scenario call any endpoint of the AirMenu API while reusing the connection you already set up.

When to use it
when none of the other AirMenu modules does what you need, for instance reading data the triggers do not return.
Watch out
you describe the request yourself, so check with AirMenu what its API expects and test each call with Run once.
AirMenu4

Trigger a Promotion

ActionIn the docs only

Here Make launches an AirMenu promotion on your behalf, so an offer can go live as a consequence of something that happened in another tool.

When to use it
when a promotion should follow an outside event, like a new contact added to your CRM.
Watch out
the documentation gives no detail on this action, so open its fields and run a test before any customer can see the result.
Need help

Need help automating AirMenu with Make?

A person reads every message.

FAQ

AirMenu and Make: common questions

01Is the AirMenu Make integration free?
Yes, AirMenu is a standard app in Make, so it works from the Free plan. That plan keeps 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of run time per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need your own AirMenu subscription, which AirMenu prices on its side.
02What do you need to connect AirMenu to Make?
An active AirMenu account and an API key from that account. In Make, you add any AirMenu module, click Create a connection, optionally name it, then paste the credentials you copied from AirMenu or follow the on-screen instructions. The connection is created once and every AirMenu module in your scenarios reuses it. If you do not have an AirMenu account yet, create one first and pick a subscription on their pricing page.
03Do the AirMenu triggers in Make react in real time?
No. Both AirMenu triggers, Watch New Order and Watch Activated Flag, are scheduled: Make checks AirMenu on the scenario's schedule and picks up what changed since the previous check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. There is no instant trigger for AirMenu, so an order appears in your scenario at the next check.
04What if the AirMenu module you need is missing in Make?
It depends on what you want to reach. The six AirMenu modules cover orders, flags and promotions. For anything else in the AirMenu API, the Make an API Call module lets you call any endpoint with the connection you already have. Keep in mind that the AirMenu documentation in Make is marked as AI-generated and may contain errors, so confirm details with AirMenu when a result surprises you. A quick Run once on a test scenario shows you what a call returns.
05Should you use Make or n8n for AirMenu?
It depends on the tool you already work with. Make offers AirMenu as a native app with 6 ready modules, including Make an API Call for the rest of the API. Many apps also have an n8n node, so check whether AirMenu has one before you choose. Base the decision on the modules each tool gives you for your use case and on the tool your team already knows, then test a small scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations