Airtable Automation Setup Guide

1. Pick the right trigger

Airtable offers these trigger types (per Airtable, Sept 2026): record created, record updated, record matches conditions, record enters view, form submitted, at scheduled time, webhook received, button clicked, plus Google Workspace and Outlook triggers.

• When record created — fires the moment a row exists. If a person is typing into a grid, it will usually fire before they finish (per Airtable). Use it for records created by forms, the API, syncs or other automations.
• When record updated — fires when a watched field changes. Choose specific fields instead of "Watch all". It does not run on record creation (per Airtable).
• When record matches conditions — fires each time a record changes into the matching state. If it stops matching and matches again, it runs again (per Airtable). This is the best default for most workflows.
• When record enters view — the same idea, but it depends on a view's filters. Airtable recommends pairing it with a locked view so a teammate can't quietly change the filters (per Airtable).
• When a form is submitted — use it for intake flows where the form is the only entry point.
• At scheduled time — the minute option runs in 15-minute steps. It does not adjust for daylight saving time on its own (per Airtable, Sept 2026).
• When webhook received — lets an outside system start the run. Limits are 100 KB per request and five requests per second, and every received webhook that starts a run counts toward your run allowance (per Airtable, Sept 2026).

2. Set it up step by step

1. Add a control field. Create a checkbox such as "Ready to send" or a single-select Status. Airtable itself suggests a dedicated "Ready" checkbox so the automation runs once per record and doesn't fire halfway through data entry.
2. Create the automation and choose the trigger. For "matches conditions" or "enters view", include the field a person fills in last in the condition (per Airtable).
3. Test the trigger against a record you created for testing (name it "TEST — do not use") rather than a live customer row.
4. Add actions and test each one. Many actions give you two choices: Generate a preview shows the result without running it, and Run as configured really runs it. That means real Slack messages, real emails and real record updates. An automation can hold up to 25 actions (per Airtable, Sept 2026).
5. Add conditional logic if paths split. Conditional groups work as If / Otherwise if / Otherwise. Only the first group whose conditions match runs, and groups can't be nested (per Airtable).
6. Toggle it On, then make a real change. Tick the Ready box on your test record and open Run history. A run should appear within moments.

3. Test without polluting real data

• Point every email or message action at your own address or a private test channel while you build. Switch to the real recipient field last.
• Use Generate a preview wherever it's offered. Save Run as configured for your test record.
• For large changes to a working system, duplicate the base and build there first, then recreate the finished automation in production.

4. Why an automation "silently never fires"

• Records already matched. Records that already meet the conditions when you turn the automation on do not trigger it. They have to leave the condition or view and come back (per Airtable). To backfill, untick and re-tick the control field.
• It toggled itself Off. Automations can switch Off on their own after an authentication problem, such as a password change on a connected account (per Airtable). Reconnect the account, then toggle it back On.
• The run allowance is used up. When the monthly limit is reached, runs stop until the limit resets on the 1st of the month. Failed runs count too (per Airtable).
• Someone edited the view. A changed filter on an "enters view" trigger quietly changes what fires. Lock the view.
• The wrong fields are watched. An "updated" trigger only reacts to the fields you selected.
• Time zones. Airtable notes that condition-based date logic runs on GMT, and scheduled times don't follow daylight saving changes.
• Loops or overlaps. An action that edits the trigger field, or two automations with overlapping conditions, can re-fire or cancel each other.

5. Plan limits (per Airtable, Sept 2026)

• Runs per workspace per month: Free 100 · Team 25,000 · Business 100,000 · Enterprise Scale 500,000.
• Automations per base: 50 on every plan. Automations that are turned off still count.
• Run history kept for: Free 2 weeks · Team 6 months · Business 1 year · Enterprise Scale 3 years.

Source: Getting started with Airtable automations. Airtable's pricing page says only that automations are capped at your plan's limit, so check the support article for current numbers.

6. Debug with Run history

Each run is marked Ran successfully, Pending, Run cancelled or Failed run. Open a failed run to find the step that broke. The usual causes are a trigger record missing a value that an action needs, a disconnected third-party account, or a script step hitting the 30-second network timeout (per Airtable). Failure emails go to the person who turned the automation on. If that person leaves the workspace, workspace owners get them instead.

FAQ

Why doesn't my Airtable automation run for records that already match?
Triggers fire when a record changes into the matching state. Records that matched before you turned the automation on are skipped. Untick and re-tick your control field to run them.

Does testing an Airtable automation send real emails or change records?
"Generate a preview" does not. "Run as configured" does, so test with your own address and a test record.

How many automation runs does Airtable allow?
Per workspace per month (Sept 2026): Free 100, Team 25,000, Business 100,000, Enterprise Scale 500,000. The count resets on the 1st, and failed runs count.

Why did my automation turn itself off?
Usually because of an authentication problem with a connected account, such as a changed password. Reconnect the account and toggle the automation back On.

Can I nest conditions inside conditions?
No. Conditional groups can't be nested, and only the first matching group runs. Use a formula field to combine logic, or split the work into separate automations.