Resources · Make integration

Air Make integrationAutomate Air with Make.

Can Make bring files into Air and keep its boards in order? Yes. The Air Make integration offers 15 action modules for assets, boards, custom fields and tags. This guide is for teams that manage visual files: it shows how to connect Air and build a first scenario.

Try the Air integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Air Make integration do?

The Air Make integration links your Air workspace to the other apps you use, through Make, a no-code tool where you assemble automations called scenarios. Each brick of a scenario is a module, and the 15 Air modules import files, place them on boards, label them with custom fields and read what the workspace already holds.

Files from links, filed on arrival. A form or a chat message hands over a link, Import asset from URL turns it into an Air asset, and Add assets to board places it where the right team will look. Nobody downloads anything by hand.

Boards that open with the project. When a deal closes in your CRM, Create board gives the client a space, Apply custom field to board marks its status, and Update board keeps its details in step as the project moves.

A workspace that stays consistent. Get custom fields and Get tags read what already exists, so Create custom field only adds what is truly missing and Apply a custom field to an asset labels each new file the same way.

What the integration does not do: Air has no trigger module in Make, so a scenario starts from another app or from a schedule. The Air documentation page on Make also warns that it was written with AI help and may contain mistakes, so test every module with Run once. For anything the list lacks, Make an API call reaches the rest of the Air API.

Air may also exist as an n8n node, and the n8n vs Make comparison lays out the criteria. To learn the editor step by step, Make training is the place, and when a run fails, open Make troubleshooting.

Connect

How do you connect Air to Make?

  1. 01

    Copy your API key in Air

    In Air, open Settings from the workspace menu, then click API Access and copy the key displayed on screen. You need an active Air account for this, and the key is what lets Make act on your workspace.

  2. 02

    Add an Air module in Make

    In your scenario, add any Air module and click Create a connection. A connection is your Air account linked to Make once. The Connection name field is optional, but a clear name helps when you look for it later.

  3. 03

    Paste the key and confirm

    Enter the API key you copied, or follow the on-screen instructions, then confirm. From then on, every other Air module in any scenario reuses this same connection without asking again.

First scenario

Build your first scenario with Air

GoalWhen a link to a file lands in another app, Make imports the file into Air and adds it to a board.

  1. 01

    Create the scenario

    From the Scenarios page in Make, create a new scenario. A scenario is the automation itself, a chain of modules. Click the + in the middle of the editor to add the first one.

  2. 02

    Start from the app that holds the link

    Pick the module of the other app where links arrive, a form or a team chat for instance. Air has no trigger in Make, so this first module is the one that starts each run.

  3. 03

    Add Import asset from URL

    Click the + on the right of the first module, search for Air and choose Import asset from URL. Click Create a connection, paste your API key, then map the link from the previous module.

  4. 04

    Place the file on a board

    Add Add assets to board next. Once the connection exists, Make can list what it reads in Air, so pick the board, then map the asset returned by the import module.

  5. 05

    Test with Run once

    Click Run once and send a real link through the first app. Each module shows the bundles it received, one bundle per item. Then check in Air that the file sits on the right board.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then turn the scenario on. Every new link now follows the same path without anyone touching it.

Modules

What each Air module does

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

Air1

Add assets to board

ActionIn the docs only

Files already stored in Air land on a board, so the team that needs them finds them in one place instead of searching the whole workspace.

When to use it
right after Import asset from URL, when every new product shot should appear on the campaign board it belongs to.
Watch out
the module works on assets that already exist in Air, so map them from an earlier module rather than typing anything by hand.
Air2

Apply a custom field to an asset

ActionIn the docs only

One file gets the label your team sorts by: this module writes a custom field value onto a single asset, so filters in Air can find it later.

When to use it
a signed contract arrives from a form and has to carry the client name before anyone opens it.
Watch out
if the field is brand new, build it with Create custom field in an earlier step, and check the result with Run once.
Air3

Apply custom field to board

ActionIn the docs only

Boards get the same treatment as files here. The module sets a custom field on a whole board, which helps when boards stand for clients, launches or seasons that you want to sort.

When to use it
a deal is marked won in your CRM and the matching board should switch to an active status.
Watch out
it acts on the board, not on the files inside it; for one file, choose Apply a custom field to an asset.
Air4

Create board

ActionIn the docs only

A new project gets its own space in Air without anyone clicking through the interface, ready to receive files from the rest of the scenario.

When to use it
a client signs or a product line starts, and its files need a home from the very first upload.
Watch out
each run creates a board, so running the scenario twice on the same data can leave two of them; test with Run once and look in Air before activating.
Air5

Create custom field

ActionIn the docs only

Your workspace gains a new field definition, the kind your team then fills on assets and boards to sort them by region, rights or status.

When to use it
you roll out a new label across Air and want the scenario to set it up before applying it anywhere.
Watch out
this changes the structure of the workspace, so keep it out of scenarios that run on every new file, or near-identical fields will pile up.
Air6

Get asset by ID

ActionIn the docs only

When you already know which file you want, this module fetches that single asset from Air and passes its details to the next module as one bundle.

When to use it
a record in another tool stores the Air asset ID, and you need the file before posting it somewhere else.
Watch out
it expects the ID itself, not a file name; if all you have is a name, start from Get assets instead.
Air7

Get assets

ActionIn the docs only

A whole set of files comes out of Air, so the rest of the scenario can work through them one by one and act on each.

When to use it
you want to push a batch of approved visuals to another app, or check what the workspace holds before creating anything.
Watch out
the module likely returns several assets; each one then runs the modules that follow, and Make counts every such execution as an operation on your plan.
Air8

Get boards

ActionIn the docs only

The boards of your workspace come back as a list, so a later step can pick the right one instead of relying on a board chosen by hand in the editor.

When to use it
the target board depends on data from another app, such as the client name on a signed order.
Watch out
it likely returns several boards, each as its own bundle; run the scenario once to see how many come back before adding actions after it.
Air9

Get custom fields

ActionIn the docs only

Reading the fields already defined in Air lets the scenario reuse them rather than guess their names, which keeps labels consistent across the team.

When to use it
before Apply a custom field to an asset, when the field to fill depends on the file type or on who sent it.
Watch out
run it ahead of Create custom field, or you may add a second field under a name that already exists.
Air10

Get tags

ActionIn the docs only

Tags are the quick labels people put on files in Air, and this module brings the existing list into your scenario for comparison or reuse.

When to use it
another app sends a keyword and you want to match it against the tags your team already uses.
Watch out
the module only reads tags; the Air list in Make has no module that applies one, so for that step look at Make an API call.
Air11

Import asset from URL

ActionIn the docs only

A file sitting behind a link becomes an Air asset, so nobody downloads it and uploads it again by hand.

When to use it
a form, a chat message or a supplier email gives you the link to a photo, a brochure or a video that belongs in Air.
Watch out
test with Run once on a real link from that app, then open Air to confirm the file arrived complete before switching the scenario on.
Air12

Make an API call

ActionIn the docs only

Anything the other modules miss is still within reach: this one calls any endpoint of the Air API with the connection you already set up, no second login.

When to use it
you need an Air feature the list lacks, such as putting a tag on a file after Get tags.
Watch out
you write the request yourself, so keep the Air API reference open next to the editor and test each call with Run once.
Air13

Poll for new assets

ActionIn the docs only

Its name points to assets newly added to Air, which makes it the natural candidate for the start of a scenario that reacts to fresh uploads.

When to use it
you want Air itself to start the flow, so you place it first and set the schedule on it.
Watch out
it is listed as an action, not a trigger; run it once alone to see what it returns, and remember the schedule runs every 15 minutes by default.
Air14

Update asset version

ActionIn the docs only

An existing Air asset receives a new version, instead of a second file sitting next to the old one and confusing everyone.

When to use it
the designer exports a corrected logo or a revised brochure, and the previous version should not float around on its own.
Watch out
point it at the right asset, which usually means finding it first with Get assets or Get asset by ID.
Air15

Update board

ActionIn the docs only

A board that already exists changes with the project, while the files it holds stay where they are.

When to use it
a campaign is renamed or refocused in your project tool, and the board in Air should say the same thing.
Watch out
to change a custom field on that board rather than its general details, the dedicated module is Apply custom field to board.
Need help

Need help automating Air with Make?

A person reads every message.

FAQ

Questions about the Air Make integration

01Is the Air Make integration free?
Yes. Air is a standard app in Make, so its modules work from the Free plan. That plan allows 2 active scenarios, runs them no more often than every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module per bundle. Air itself requires an active account; its prices are on the Air pricing page.
02What do you need to connect Air to Make?
An active Air account and its API key. In Air, open Settings from the workspace menu, click API Access and copy the key shown on screen. In Make, add any Air module to a scenario, click Create a connection, give it a name if you like, then paste the key. That connection is saved once and reused by all 15 Air modules, so the step never has to be repeated for another module or another scenario.
03Does the Air Make integration react in real time?
No. Air has no trigger module in Make, neither scheduled nor instant, so nothing in Air starts a scenario on its own. There are two ways around it. Put another app's trigger first, a form or a CRM for example, then chain the Air modules after it. Or try Poll for new assets as the first module and set the schedule on it: every 15 minutes by default, down to 1 minute on a paid plan. A Run once test shows what that module returns before you rely on it.
04What if an Air module is missing in Make?
Use Make an API call. It sends a request to any endpoint of the Air API with the connection you already have, so there is no second login. A typical case: the list includes Get tags but no module that applies a tag, and a direct request can fill that gap if the Air API offers it. Keep in mind that the Air documentation page on Make says it was produced with AI and may contain errors, so check the Air API reference and test with Run once.
05Make or n8n for Air?
It depends on where your automations already live. On Make, Air brings 15 action modules including Make an API call, one connection shared by all of them, and a Free plan that lets you test with 2 active scenarios. The same app often has an n8n node as well, so check that side before choosing. Fair criteria are the modules your use case needs, the way your team likes to build, and the tool it already knows. Neither tool is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations