Skip to main content
Question

Clarification on 429 errors – will upgrading from Free to Team eliminate API rate issues?

  • February 25, 2026
  • 2 replies
  • 36 views

Hi everyone,

 

I’m currently running multiple automations through Make (formerly Integromat), and I’m receiving recurring 429 rate limit errors when writing to Airtable.

 

Here’s my setup:

 

• Multiple bases (each client has a separate base)

• Automations triggered via webhook

• In some scenarios, a single workflow performs 4–6 Airtable operations in sequence (search, create, update, etc.)

• Sequential processing enabled in Make

• Free plan currently

 

From what I understand, Airtable has:

 

• 5 requests per base per second rate limit

• 1,000 API calls per month on Free

• 100,000 per month on Team

 

My question is specifically about the rate limit behavior:

 

If I upgrade from Free to Team, does that change the per-second rate limit (5 requests per base per second), or does that limit remain the same regardless of plan?

 

In other words:

 

If I occasionally execute 6 Airtable operations within the same second inside one scenario, will upgrading prevent 429 errors, or is the 5 requests/sec limit enforced equally on all plans?

 

I want to make sure I’m addressing the correct constraint (monthly API cap vs. per-second rate limit).

 

Any clarification from someone who has experience scaling automations with Airtable would be greatly appreciated.

 

Thanks!

2 replies

TheTimeSavingCo
Forum|alt.badge.img+31

The 5 requests per base per second limit applies to all plans I’m afraid

https://support.airtable.com/docs/managing-api-call-limits-in-airtable#understanding-rate-limits

 


nroshak
Forum|alt.badge.img+9
  • Inspiring
  • February 26, 2026

If no single automation is jamming all 6 operations into one second, but you’re running a lot of concurrent automations, you could also be hitting the limit of 50 requests/second for all traffic using that personal access token or service account. (same link as above)

-Natalka