Airtable module fails to load table list (429 error) on one specific base

[gerald2]

What is your goal?

Use the Airtable “Search Records” module as a trigger to retrieve records filtered by a status from an existing base.

What is the problem & what have you tried?

For one specific Airtable base (“Matrice”), the Table dropdown in the Airtable > Search Records module fails to load and shows “Failed to load data (429)”.

The same Airtable OAuth connection works correctly with another older base.
The issue only occurs on this specific base.
The base is not duplicated and belongs to my personal Airtable account.

I have tried:

• Recreating the OAuth connection
• Using a Personal Access Token
• Testing with another base (works fine)

The base is visible in the Base dropdown, but Make cannot load its tables.
This blocks my automation.
This issue seems related to a previously reported Airtable incident marked as resolved, but it is still reproducible on my account.

Error messages or input/output bundles

Error: Failed to load data (429)

Screenshots (scenario flow, module settings, errors)

[Henk-Operative]

Hi @gerald2,

Welcome to the community. A 429 error is a rate-limiting error. Make cannot fetch the table(s) because Airtable prevents your connection from executing calls.

Are you on the free Airtable plan? That only includes 1000 calls per month. The Team plan includes 100k per month. So this is a matter of waiting it out or upgrading I am afraid.

Cheers,

@Henk-Operative

[gerald2]

Hi Henk, thanks for your reply.

Yes, I am on the free Airtable plan, however I don’t think this is a global rate-limit issue.

The same OAuth connection works immediately with another Airtable base in the same account.
The 429 error happens only when Make tries to load the table list (schema) of this specific base, before any scenario run or record fetch.

If it were a monthly API quota issue, I would expect:

• the error to affect all bases
• or to occur during record retrieval, not when loading the table dropdown

This seems more related to an issue fetching the base schema (meta/tables) for this specific base.

Could this be escalated or checked internally? I can provide the Base ID if needed.

Thanks!

[gerald2]

Thanks for the clarification.

I’ve double-checked my Airtable integrations and now have two clean, separate Make integrations created the same day:

• One for workspace “PASSION DU CODE” → base “Projet e-commerce” (works perfectly)
• One for workspace “ALEGRIA” → base “Matrice” (table list still fails to load with 429)

Both use the same Airtable account, same Make account, same OAuth flow, and the same permissions (data + schema access).

This confirms the issue is isolated to the “Matrice” base schema, not a global API quota or plan limitation.

Could this be escalated for internal investigation on the Airtable/Make side?
I can provide the Base ID if needed.

[Henk-Operative]

Hi @gerald2,

Thanks for the clarification. If it were an API limit issue, I would also expect it to be enforced for the complete Airtable account regardless of which base you choose.

Also to prevent a misconception, I am not in employ of Make. I don’t have power to investigate or escalate on Make’s side.

There might be a chance that Make fires too much requests at once while trying to fetch tables. E.g. if Module fetches both the list and details per base while you have more than 50 bases ( Airtable Web API )

How many basis do you manage? You can see the actual requests Make sends with this DevTool, which might give you more insight in a) what/how many calls Make is sending and b) the actual response/error coming from Airtable.

Chrome Extension:
Make DevTool - Chrome Web Store
Tutorial:
Introduction to Make Chrome DevTool (formerly Integromat DevTool)

Cheers,
@Henk-Operative

[gerald2]

Thanks for the clarification, understood.

To answer your questions:

• I manage far fewer than 50 Airtable bases on this account.
• The issue is reproducible immediately, even on a fresh page load, before any scenario run or heavy activity.

At the moment the error occurs simply when opening the Airtable module and loading the table dropdown for this specific base (“Matrice”), while another base works instantly under the same conditions.

I’ll take a look at the Make DevTool to inspect the actual requests and Airtable responses and will report back if I see anything relevant.

[mszymkowiak]

Hello,

Please try to make a custom API call using the Make an API Call module.

URL

v0/meta/bases/{baseId}/tables

where {baseId} should be changed to your base ID - you can find it in your URL - it starts with app

https://support.airtable.com/docs/finding-airtable-ids#finding-base-ids

Method

GET

If that works for you (you get 200 instead of 429) - please contact make.com support directly- https://www.make.com/en/ticket.
We do not have the ability to access your account and debug modules on your account.

If error will still occur while making direct call please contact Airtable support- Contacting Airtable

[gerald2]

Update: I tested a direct API call using Make → Make an API Call:

GET v0/meta/bases/{baseId}/tables

It also returns a 429 RateLimitError with Origin = Airtable.
So the issue is reproducible outside of the Airtable module.

I’ll contact Airtable support with this evidence.
Thanks for your help.

[mszymkowiak]

Thank you for confirming!

Please let us know when you find a solution with Airtable’s team - this will help others with similar issues.

Meanwhile, you can also check if your table and field names do not contain any special characters- I think that could be the case.