Resources · Make integration

AITable Make integrationAutomate AITable with Make.

Can a new AITable record or form entry start work in your other tools on its own? The AITable Make integration gives you 6 modules: 2 instant triggers, 3 actions and 1 search. This guide is for ops and marketing people who live in AITable and want a working scenario without writing code.

Try the AITable integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AITable Make integration let you automate?

The AITable Make integration links your AITable account to Make, a visual tool where you chain apps together without code. AITable can wake a Make scenario the moment a record is created or a form is submitted, and Make can create, read, update or look up records in your datasheets in return.

Lead intake that sorts itself. A prospect fills in your AITable form, Watch New Form fires, and the answers travel to your CRM or your team chat. If the lead already sits in another datasheet, Search Records finds it first so nobody works it twice.

A status that stays in sync. When a deal changes stage in another app, Update a Record rewrites the matching AITable row by its record ID, so your datasheet reflects reality without anyone retyping it.

New rows that trigger follow-up. Watch New Record notices each row your team adds, and Get a Record pulls the full details when a later step needs them, for example to fill a welcome email.

What Make does not offer here: there is no Make an API Call module for AITable, so you are limited to these 6 modules. The same app often has an n8n node too; if you are weighing both tools, read n8n vs Make. To see what each Make plan includes, check Make pricing, and if you prefer to learn the editor properly, the Make training covers it from scratch.

Connect

How do you connect AITable to Make?

  1. 01

    Copy your API token in AITable

    In AITable, open your user account dashboard, click the Settings tab in the sidebar, then the API section. Copy the API token shown there. Make needs it to act on your behalf, and you need an active AITable account to see it.

  2. 02

    Add an AITable module in Make

    In your scenario, add any AITable module and click Create a connection. A connection is your AITable account linked to Make once, then reused by every AITable module. You can give it a name in Connection name, which is optional but handy once you have several connections.

  3. 03

    Paste the token and save

    Paste the token you copied into the credentials field, or follow the on-screen instructions, then confirm. Make now lists the datasheets it can reach, so you pick them from a menu instead of typing identifiers by hand.

First scenario

Your first scenario with AITable and Make

GoalWhen someone submits your AITable form, Make creates a matching record in a second datasheet.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add its first module. A scenario is the chain of modules Make runs for you.

  2. 02

    Add Watch New Form

    Search for AITable, pick Watch New Form, click Create a webhook, then Create a connection and paste your API token.

  3. 03

    Add Create a Record

    Click the + to the right of the trigger and choose Create a Record. Select the target datasheet from the list and map the form answers into its fields.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Open the bubble above each module to read the bundle it received, meaning the single item passed along.

  5. 05

    Switch it on

    When the new record looks right, switch the scenario on. The trigger is instant, so each new form entry starts a run without waiting for a schedule.

Triggers

Which AITable triggers can start a scenario?

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

AITable1Watch New Form

Watch New Form

Instant trigger

In Make“Triggers when a form is submitted and received.”

Watch New Form starts your scenario every time someone submits an AITable form, handing Make the answers as one bundle. You get the submission itself, ready to route anywhere, instead of hunting for the new row afterwards.

How it fires
instant, AITable calls Make through a webhook as soon as the form is submitted, so no polling schedule is involved.
When to use it
a contact or quote request form whose answers should reach sales or support the moment they arrive.
Watch out
click Create a webhook before Create a connection, as the AITable documentation asks, or the setup stays incomplete.
AITable2Watch New Record

Watch New Record

Instant trigger

In Make“Triggers when a new record is created.”

Watch New Record fires whenever a new row appears in AITable, whoever or whatever created it. It suits datasheets your team fills by hand, where a form is not the entry point, and turns each fresh row into a bundle Make can act on.

How it fires
instant, AITable calls Make through a webhook as soon as the record is created.
When to use it
a project tracker where each new line should open a task or notify the owner.
Watch out
if a later step of the same scenario creates rows in that datasheet, you can start a loop, so point it at a different datasheet.
Modules

What can Make do in AITable?

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

AITable1

Create a Record

Action

In Make“Creates a record in a datasheet.”

Create a Record adds a fresh row to the datasheet you pick, filled with data mapped from earlier modules. Your AITable base grows by itself as things happen in other apps.

When to use it
logging every new order, signup or ticket from another tool into one AITable view your team already reads.
Watch out
when the same person could arrive twice, run Search Records first, or you may end up with two rows for one contact.
AITable2

Get a Record

Action

In Make“Gets a record by record ID.”

Get a Record fetches one row when you already hold its record ID, giving later modules every value stored in it. Think of it as opening a known file rather than searching a cabinet.

When to use it
a trigger hands you only an ID and the next step needs the full row, such as an email that quotes several fields.
Watch out
without a valid record ID it has nothing to fetch; use Search Records instead.
AITable3

Update a Record

Action

In Make“Updates a record by record ID in datasheet.”

Update a Record rewrites an existing row, located by its record ID, with new values from your scenario. The datasheet stays current without anyone editing cells by hand.

When to use it
marking an invoice as paid or moving a lead to a new stage when another app reports the change.
Watch out
the ID must come from an earlier module, usually Search Records or a trigger, or Make will not know which row to touch.
AITable4

Search Records

Search

In Make“Returns records by fields or formula.”

Search Records looks through a datasheet by field values or by a formula and returns the matching rows, which can be none, one or many bundles. It is how you answer the question "does this already exist?" before acting.

When to use it
checking whether an email address is already in your contacts before Create a Record adds it.
Watch out
every match continues through the next modules, so a loose search can update many rows at once.
Need help

Need help automating AITable with Make?

A person reads every message.

FAQ

AITable and Make: common questions

01Is the AITable Make integration free?
Yes, on the Make side. AITable is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, and caps each run at 5 minutes. Paid plans lift the interval to 1 minute, remove the cap on active scenarios and count usage in credits, one per operation, which is one module processing one bundle. Your AITable subscription is a separate matter: you need an active account and an API token, and the AITable pricing page tells you what your plan includes.
02What do you need to connect AITable to Make?
You need an active AITable account and its API token. Find it in AITable by opening your user account dashboard, then the Settings tab in the sidebar, then the API section, and copy the token shown. In Make, add an AITable module, click Create a connection, name it if you like and paste the token. For Watch New Form or Watch New Record, click Create a webhook first, since those instant modules receive calls from AITable. The connection is then reused by every AITable module in your scenarios.
03Do AITable triggers in Make work in real time?
Yes. Both AITable triggers, Watch New Form and Watch New Record, are instant: AITable calls Make through a webhook as soon as a form is submitted or a record is created, and the scenario starts right away. That is the lightning badge you see on the module. You do not wait for the scenario schedule, which on a new scenario defaults to every 15 minutes and only applies to scheduled triggers. Remember to switch the scenario on after testing with Run once, otherwise the webhook receives calls that nothing processes.
04What if the AITable module you need is missing in Make?
It depends on what you need. AITable in Make has 6 modules and no Make an API Call module, so you cannot send a custom request to AITable from this app. Often a mix of existing modules covers the gap: Search Records followed by Update a Record handles most edits without an ID in hand. If your case goes further, another app in your scenario may hold the data you need, or the team can look at your use case with you. The official documentation also warns that some content may contain mistakes, so check important details with AITable directly.
05Should you use Make or n8n for AITable?
It depends on the tool your team already uses. Make gives AITable 6 modules, including 2 instant triggers for new forms and new records, and a visual editor where you test each step with Run once. The same app often has an n8n node as well, so the choice rarely comes down to AITable itself. Compare which modules each tool offers for the actions you need, and pick the platform where the rest of your automations already live. Keeping everything in one place is usually easier to maintain than splitting flows between two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations