What we do
Tools
Industries
Department
How we workLet's talk →
Home/Airtable/When Airtable Automations Hit Their Limits
Airtable

Airtable Automations: Why a Run Fails, and Which Trigger to Use

You open an automation's run history and there's a red failure, or a notice that the workspace has used its runs for the month. Airtable Automations are a trigger plus one or more actions, built inside a base, and nearly every problem traces back to three things: the trigger you picked, the monthly run allowance, and the limits on the Run a script action. Here's each one, and what to do about it.

How an automation is put together

Build it from the Automations tab at the top of the base: one trigger, then as many actions as the job needs underneath it.

Triggers: a record is created, updated, enters a view or matches conditions, a form is submitted, a scheduled time arrives, a button is clicked, or a webhook is received. Google Workspace and Outlook triggers are there too.

Actions: create, update, find or delete records, send an email, post to Slack or Microsoft Teams, act in Jira, Salesforce or Google Workspace, and Run a script for anything the others can't express.

One trigger firing is one run, whether its actions succeed or fail. That's the number your plan's monthly allowance counts.

Reasons the run history shows a failure

The limits here come from Airtable's own help pages on the Run a script action and on automation run limits.

The script ran out of time

How you'll know: The run fails partway through a loop, usually on a big table or while waiting on a slow outside API.

Fix: A script action has a time cap, and a single fetch to another service gives up after 30 seconds. Split the work across several script actions, or have the script pass the job to an outside service and finish quickly.

The script hit its request ceiling

How you'll know: A script that calls another API once per record stops after a few dozen records.

Fix: One script action gets 50 fetch requests, 30 selectRecords queries, 512 MB of memory, and up to 15 writes a second, each covering up to 50 records. Batch the writes, fetch in bulk, or move the loop outside Airtable.

The workspace used up its monthly runs

How you'll know: Airtable tells you the allowance is spent. It resets on the first day of the month.

Fix: The allowance is per workspace: 100 runs a month on Free, 25,000 on Team, 100,000 on Business and 500,000 on Enterprise Scale. A "record updated" trigger watching every field is the usual culprit, so limit it to the fields that matter, or switch to "matches conditions".

The trigger fired before the record was ready

How you'll know: A "record created" automation runs while a teammate is still filling in fields, so the action works on blanks.

Fix: Use "matches conditions" or "enters a view" with a filter that requires the fields you need. The run then waits until the record is complete.

Run a script isn't in the action list

How you'll know: You can add every action except the script one.

Fix: Airtable's help page says the script action isn't available during a Team plan trial, and lower plans get tighter limits.

A change in another system was supposed to start it

How you'll know: You're running a scheduled automation every hour just to catch what changed somewhere else.

Fix: The When a webhook is received trigger lets the other system start the run directly. If that system can't send webhooks, or the job needs retries, sign-in flows or paged results, build it as a small service on the Airtable API instead.

Which trigger fits the job

The job Trigger to use Watch for
Tell someone a new request has landed When a form is submitted, or when a record is created Form submissions arrive complete. Records typed in by hand often don't, at first.
Act once a record reaches a stage When a record matches conditions, or enters a view A record that drops out of the condition and comes back fires again.
React to an edit in one field When a record is updated, limited to the fields you care about Watching every field spends runs on edits nobody needed to act on.
A nightly or weekly report At a scheduled time One run per schedule, but the script still has to finish inside its limits.
An approval a person decides on When a button is clicked Nothing fires until someone chooses to, which is the point.
Another system says something changed When a webhook is received The other system has to send it. If it can't, something has to watch that system and send it.

Inside the base, or beside it

Keep it native

The job starts and ends in one base

  • Status changes, record links, reminder emails and Slack posts.
  • A script that tidies or formats a handful of records at a time.
  • Anyone on the team can open it, read it and change it without a developer.
Build it outside

The job has to land in another system

  • An approval clicked in Airtable that also has to update the matching record in accounting or the CRM, not just email someone to do it.
  • A scheduled report that should retry when it fails and reach the system that acts on it, instead of an inbox.
  • Pulls from an API that returns data in pages, or needs sign-in more involved than a key in a header.

Most bases end up with both: Automations for the in-base steps, and an outside job for the part that talks to accounting, a CRM or a warehouse, started by a webhook or a button.

Questions people ask

What triggers can an Airtable Automation use?

A record being created, updated, entering a view or matching conditions, a form submission, a scheduled time, a button click, and an incoming webhook, plus Google Workspace and Outlook triggers. Each automation has exactly one trigger.

Can Airtable Automations send data to another system?

Yes. There are built-in actions for Slack, Teams, Jira, Salesforce, Google Workspace and Outlook, and Run a script can call almost any API with fetch. What you don't get is a retry when the other side is down, or room for long paged pulls inside the script's limits. That's usually where an outside job takes over.

Do I need to know how to code to build an Airtable Automation?

Not for trigger-and-action setups, which are point and click. Run a script needs some JavaScript, and it's the action you'll reach for when you need branching, loops over many records, or a call to an API that has no built-in action.

Is there a limit on how many Automations I can run?

Yes, two kinds. Runs are capped per workspace each month (100 on Free, 25,000 on Team, 100,000 on Business, 500,000 on Enterprise Scale), and failed runs count. Each base also has a cap on how many automations it can hold.

What's the difference between an Airtable Automation and the Airtable API?

An Automation runs inside Airtable and starts from something that happens there, or from a webhook sent to it. The API works the other way round: a system outside Airtable reads and writes your base on its own schedule. Many good setups use an Automation to start work and the API to finish it.

Who builds the part an Airtable Automation can no longer handle?

n-frames picks it up from there. We build the hosted job your automation calls, with retries, paging and alerts, and write results back to the record that started it, so the base stays where your team works.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.