Automations
How many automations a base can hold, how runs are counted, and how triggers, loops and failures behave.
| Limit | Business |
|---|---|
| Automations per base | 150 |
| Automation runs per workspace per month | 100,000 |
| Email to non-collaborators per day | 1,000 unique addresses |
| Run history | 1 year |
| Actions per automation | 25 (community figure, not on the official pages) |
What counts
Turned-off automations count against the 150. Only deleting an automation frees a slot.
A run is counted each time a trigger fires, on success or failure. The counter resets on the first day of the month. The quota belongs to the workspace, so every base shares it.
Triggers
A formula-field trigger is checked about every 5 minutes while the base is open. It is checked about once an hour otherwise.
“When record updated” can watch all fields or a chosen set. Records that already match a condition do not fire “when record matches conditions”. Triggers are not retroactive.
A view of a synced table is a valid trigger surface. Airtable does not document whether a change delivered by the sync fires “when record updated”.
A webhook is an address that receives each change as it happens. A webhook subscription can filter by source (client, public API, form, automation, system, sync) and by watched fields.
Loops
An automation can trigger another. A loop has no automatic cutoff. It runs until the workspace quota is spent.
Failures
No automatic retry is documented. A failed run stays failed. Only a manual rerun exists.
Sources
- Getting started with Airtable automations: automations per base, runs per month, email to non-collaborators, formula triggers, run history. Verified 2026-11-05.
- Troubleshooting Airtable automations: looping automations run until the workspace limit is exhausted. Verified 2026-09-14.
- Webhooks specification: source and field filters. Verified 2026-09-14.