Resources · Make integration

Airtable Make integrationAutomate Airtable with Make.

Your base should start the work, not just store it. The Airtable Make integration gives you 13 modules, the bricks of a scenario, which is the automation you build in Make. Two of them listen for changes, eleven act on your records. This page takes you to a live one.

Try the Airtable integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Airtable Make integration actually do?

Airtable holds your records. Make runs the steps around them. Once the two are linked, a row that appears or changes in a view can start a chain: a record created in another table, a lookup to find the right line, a batch of rows updated in one pass. Airtable stays the place where the data lives. Make becomes the hands that move it.

Intake that files itself. A new line lands in a view, Watch Records picks it up, and Create a Record writes the matching entry in the table your team actually works from. Nothing gets retyped.

A base that stays clean. Search Records looks for the line that already exists, and Upsert a Record updates it when it does or creates it when it does not. Two modules, and most of the manual tidying goes away.

Bulk edits without the copy paste. The advanced modules handle several records in one pass: Bulk Create Records (advanced) for a whole list, Bulk Update Records (advanced) for a status that has to move on many rows at once.

What Make will not do here: the modules in the Records group are documented as available on the Airtable Team plan and the tiers above it. No setting inside Make gets around that, so it is worth checking before you build.

Airtable also exists in n8n. If the tool choice is still open, the n8n vs Make comparison and the Airtable n8n integration page hold the other side, and Make training is there when you would rather be walked through it.

Connect

How do you connect your Airtable account to Make?

  1. 01

    Add a module first

    Open a scenario, drop in any Airtable module, then click Add next to the Connection type field and choose Airtable OAuth. An Airtable account is all you need. The connection, meaning your account linked to Make, gets reused by every Airtable module you add later.

  2. 02

    Name it and save

    The Connection name field is optional, though naming it helps once a scenario uses more than one Airtable connection. Leave Show Advanced Settings off unless you registered your own OAuth credentials, then click Save.

  3. 03

    Grant access to a base

    Make opens the Authentication screen. Click Add a base, choose the base your scenario will touch, then click Grant access. The documented minimum is three scopes: data.records:read, data.records:write and schema.bases:read.

First scenario

Your first scenario, step by step

GoalWhen a new record shows up in a view, Make creates the matching record in another table.

  1. 01

    Create the scenario

    From the Scenarios page, start a new scenario and click the + to place the first module. Search Airtable by name and pick Watch Records.

  2. 02

    Point the trigger at a view

    Choose the base and the view to watch. Watch Records leans on a Created Time or Last Modified Time field, so one of those two has to exist in the table.

  3. 03

    Add the action

    Click the + on the right of the trigger and add Create a Record. Drag the values coming out of the first module into the fields of the second one. That mapping is the whole link.

  4. 04

    Test with Run once

    Click Run once and add a line in the watched view. Each module then shows the bundles it received, a bundle being one record on its way from one module to the next.

  5. 05

    Schedule it and switch it on

    Set the clock on Watch Records. A new scenario runs every 15 minutes by default, and 15 minutes is the floor on the Free plan. Then flip the scenario on.

Triggers

What can start your scenario

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

Airtable1Watch Records

Watch Records

Scheduled trigger

In Make“Returns all newly created or updated records in a view (requires "Created Time" or "Last Modified Time" fields).”

Watch Records keeps an eye on one view and hands your scenario the records that were just created or updated.

How it fires
on a schedule. Make asks Airtable at the rhythm set on the first module, so nothing here happens to the second.
When to use it
a view that collects incoming requests, where every new line has to become a task somewhere else.
Watch out
the module leans on a Created Time or Last Modified Time field. Without one of them it cannot tell what is new.
Airtable2Watch Responses

Watch Responses

Instant trigger

In Make“Triggers when a new response is submitted.”

Watch Responses waits for a new response to be submitted and drops it straight into your scenario.

How it fires
instantly. Airtable calls Make through a webhook, the address Make opens for the app, the moment the response arrives.
When to use it
anything a person is waiting on, like an answer that has to reach a channel while the sender is still on the page.
Watch out
it covers responses, not every edit made to a record. For those, Watch Records is the one that reports back.
Modules

What Airtable can do inside a scenario

Airtable gives you 11 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Records

10 modules

Available on the Team plan and all higher Airtable tiers. See the Airtable pricing page.

Airtable1

Search Records

Search

In Make“Searches for specific records or returns all records.”

Search Records asks your base a question and brings back the lines that answer it: none, one, or a whole list.

When to use it
before you write anything, to check whether the customer, the invoice or the ticket already has a row.
Watch out
every result found travels on through the rest of the scenario, which then replays once per record. Narrow the search when you can.
Airtable2

Get a Record

Action

In Make“Retrieves a single record by its ID.”

Get a Record pulls one single line by its ID, with all of its fields.

When to use it
when an earlier module already handed you the ID and you need the rest of the row before deciding what happens next.
Watch out
no ID, no record. If all you hold is an email or an order number, run Search Records first.
Airtable3

Create a Record

Action

In Make“Creates a new record in Airtable.”

Create a Record adds one new line to the table you choose. One pass, one record.

When to use it
the first automation most teams build, where a form, an email or another app turns into a row without anyone typing.
Watch out
it creates every single time it runs. If the same line can arrive twice, Upsert a Record is the safer pick.
Airtable4

Update a Record

Action

In Make“Updates a record by its ID.”

Update a Record changes the fields of a line that already exists, found by its ID. Whatever you leave alone stays as it was.

When to use it
a status that moves forward, a date that gets confirmed, a total recalculated after a payment.
Watch out
the ID has to come from somewhere, usually the trigger or a search placed just before.
Airtable5

Upsert a Record

Action

In Make“Creates new or updates an existing record.”

Upsert a Record does both jobs in one module: it updates the line when it finds it, and creates it when it is missing.

When to use it
a sync that keeps running over the same source, where a second copy of the same contact has no business existing.
Watch out
the module decides on its own between create and update, so a loose match overwrites the wrong line.
Airtable6

Delete a Record

Action

In Make“Deletes a record by its ID.”

Delete a Record removes one line from your base, by its ID.

When to use it
a cleanup step at the end of a flow, once the row has been copied elsewhere and has no reason to stay.
Watch out
there is no going back inside the scenario. Test with Run once on a line nobody cares about before you switch anything on.
Airtable7

Bulk Create Records (advanced)

Search

In Make“Сreates multiple records.”

Bulk Create Records (advanced) writes several lines in a single module pass instead of one per record.

When to use it
an import, a list that arrives in one piece, a batch prepared earlier in the scenario.
Watch out
it is the advanced version and expects the full list at once. Build it up gradually and read what comes out with Run once.
Airtable8

Bulk Update Records (advanced)

Search

In Make“Updates multiple existing records.”

Bulk Update Records (advanced) applies one change to a whole group of existing lines.

When to use it
a status to move on every row a search just returned, without walking through them one by one.
Watch out
each line still needs its ID. Pair it with Search Records so the group is built from what the base really holds.
Airtable9

Bulk Upsert Records (advanced)

Search

In Make“Upserts multiple records.”

Bulk Upsert Records (advanced) takes a list and sorts it out: lines already there get updated, missing ones get created.

When to use it
a catalogue or a contact list refreshed from another tool, pushed whole while the module works out the difference.
Watch out
the longer the list, the harder a mistake is to spot. Start on a handful of lines.
Airtable10

Bulk Delete Records (advanced)

Action

In Make“Deletes multiple records.”

Bulk Delete Records (advanced) removes a group of lines in one call.

When to use it
a staging table emptied once its rows have left for their final home.
Watch out
nothing asks you to confirm. Build the list with a search, look at it with Run once, and add the delete last.

Other

1 module
Airtable11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Airtable API with the connection you already set up.

When to use it
the corner of Airtable no module covers, once the other twelve have been ruled out.
Watch out
the scenario stops reading by itself at that point. Keep it for the step that truly needs it and let the named modules do the rest.
Need help

Need help automating Airtable with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Airtable Make integration free?
Yes, from the Free plan, within its limits. Airtable is a standard app in Make, so it is there without buying an add-on. What the Free plan caps is the running: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, 512 MB of transfer. Every module that runs on one record counts as one operation, the unit Make deducts from your plan, so a search that brings back a long list followed by an update costs far more than two. Paid plans bring the interval down to 1 minute and lift the scenario count.
02What do you need to connect Airtable to Make?
An Airtable account and the right to open a base. In Make you add an Airtable module, click Add next to the connection type, choose Airtable OAuth and save. Make then shows the authentication screen, where you add the base and grant access. The documented minimum is three scopes: read records, write records, read the base schema. One thing worth checking before you build: the modules in the Records group, which is almost every module on this page, are documented as available on the Airtable Team plan and the tiers above it.
03Does the Airtable trigger react in real time?
It depends which one you pick. Watch Records is scheduled: Make asks Airtable at the rhythm set on the first module, every 15 minutes by default, and 15 minutes is the floor on the Free plan, so a change can wait that long before the scenario sees it. Watch Responses is instant: Airtable calls Make through a webhook as soon as a response is submitted, and the scenario starts right there. On a paid plan, the scheduled interval drops to 1 minute.
04What if a module is missing or a limit gets in the way?
Make an API Call covers the gap. It reaches any endpoint of the Airtable API with the connection you already created, so whatever the twelve named modules do not handle stays reachable without leaving the scenario. Two things it does not solve: the Records modules are still documented from the Airtable Team plan up, and the Make Free plan limits are the same whichever module you use. Check both points before you build a workaround, then keep the named modules for everything they already do well.
05Make or n8n for Airtable?
It depends on who will maintain it. Make is visual, and a chain of modules can be shown to someone who does not code, which is why most teams start there. n8n looks more like a development tool, with self-hosting and code nodes, at the cost of a steeper start. Airtable sits on both sides with a comparable set of record operations. If the automation belongs to an ops or marketing team, Make wins on the day to day. If it lives next to your other services and a developer owns it, n8n is the honest answer.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations