Hitting Airtable's Automation Limit? Here's What You Can Do

Airtable now allows this many automations per base:

These are limits for unique automations. Airtable counts turned-off automations too, and the limit applies to each base. The number of times those automations can run each month is a separate limit.

Open your base and click Automations to see how many more automations you can add.

Before You Start: Audit What You Already Have

Before trying any of the workarounds below, spend 10 minutes reviewing your existing automations. Most bases that hit the limit have a fair amount of redundancy that can be cleaned up first.

Open your automations panel and look for:

Disabled automations that are no longer used. These still count toward your limit. Delete anything that has been off for more than a few weeks and is not going to be turned back on.

Automations that run the same action with different values. For example, five automations that each send a different email notification depending on a status value. These can often be collapsed into one.

After a cleanup pass, you may recover several slots without restructuring the rest of your base. Do this first before committing to a bigger solution.

If you still need more slots after the cleanup, start by combining automations that use the same trigger.

1. Merge Automations Using Conditional Logic

This is the first thing to try and usually recovers the most slots with the least effort.

Airtable automations support conditional logic inside a single automation. One trigger can branch into multiple paths depending on field values, which means one automation can replace five that were previously doing the same thing with different conditions.

How to do it

1. Identify a group of automations that all share the same trigger, such as a change to a Status field.

2. Create a new automation with that trigger.

3. After the trigger, add a Conditional step instead of jumping straight to an action.

4. Set the condition for the first branch, such as Status is In Review.

5. Add the action for that branch.

6. Click Add branch to add the next condition.

7. Repeat for each of the original automations you are replacing.

8. Test the new automation, then delete the original automations one by one.

This approach works especially well for notification automations, status-based emails, and anything where the trigger is the same and only the action varies.

2. Replace Daily Batches With a Single Script

If you have multiple automations that all run on a schedule, such as every day, every hour, or every Monday, these are strong candidates to be replaced with a single scripting automation.

Instead of ten automations that each check a different condition at 9am and do something if it is true, one script runs at 9am, loops through your records, checks every condition, and handles every action in one pass.

What this looks like in practice

Say you have these four scheduled automations:

• Every day at 9am: if a task is overdue, send a Slack message.
• Every day at 9am: if a deal has been in Proposal Sent for more than 7 days, update the status to Follow Up.
• Every day at 9am: if a subscription renewal is within 14 days, create a reminder record.
• Every day at 9am: if a project has no assigned owner, send an email to the manager.

All four can be replaced with one automation triggered at 9am that runs a script handling all four checks in sequence.

If you have not written Airtable scripts before, you can describe what each automation does to an AI tool and ask it to write the script. The pattern is usually: fetch records, loop through them, check conditions, and run actions.

For help with writing scripts that process large numbers of records without timing out, see How to Deal With Airtable's 30-Second Script Limit in Automations.

The Run a script action is not available on the Free plan, so use this option only when your plan supports it.

3. Split Your Base Into Multiple Bases

If your automations fall into natural clusters that handle different parts of your operation, splitting them across multiple bases gives each base its own plan limit instead of one shared pool.

This works best when the workflows are genuinely separate. A base for client onboarding, a base for project delivery, and a base for invoicing each have their own logic that does not heavily depend on the others.

What to watch out for

Synced tables are read-only in the destination base. When you split a base, you need to decide which base owns each piece of data and make sure all the automations that need to write to that data live in the same base where the data lives.

If you have workflows where the same record needs to be updated by automations in two different bases, syncing will not help you. You would need to use Make to write back to the source base instead.

For bases where the workflows are genuinely independent, splitting is clean and does not require any external tools.

4. Move Complex Automations to Make

Make connects to Airtable through webhooks and the API. Moving some of your automations out of Airtable and into Make frees up slots for the simpler automations that are easier to manage natively.

The most effective approach is to identify your most complex automations first, such as the ones with multiple steps, calls to external services, or conditional logic that is getting hard to manage. These are the ones that benefit most from being in a visual workflow tool and that free up the most capacity when moved out.

A single Make scenario can often replace several chained Airtable automations. You keep the simple triggers and actions in Airtable, and anything with more complexity lives in Make where it is easier to build and debug.

For an example of connecting Make to Airtable through webhooks, see How to Trigger Make Webhooks Automatically from Airtable.

Choosing Your Approach

Start with the audit and the conditional logic merge. These cost nothing and usually recover enough slots to keep going for a while.

If you are still short after that, look at whether your scheduled automations can be collapsed into scripts. That tends to be the next biggest win for most bases.

If you have genuinely hit the automation limit, splitting the base or moving some work to Make are both solid options, depending on how independent your workflows are.

For the related problem of running out of monthly automation runs rather than hitting the unique automation limit, see How to Limit Automation Runs in Airtable to Save Quota.