What happens when you run out of Automations?

Because you can’t purchase more Automations on the Pro Plan in the event you run out (like integromat/zapier), what happens to your workflow? Is everything halted?
Upgrading to enterprise would not be an option due to extreme price difference.

For example - Say I have my automations set for my entire workflow working great, but I accidentally trigger an automation that uses a ton of unnecessary automations… oops… my fault and understand and wish I can buy more to pay for that mistake, but I can’t.
Now I am out of automations and almost have an entire month left with zero automations :frowning: and all my workflows are stopped.

I just want to find out the “what if” and hope never end up in that situation :slight_smile:


This is a great question. I’d like to know what happens in this situation, too.

1 Like

So, this is precisely why there should be no limits on automations for paid users. Airtable should cherish users who avoid API and glu-factory integrations that pummel servers constantly seeking info about record changes and states. Automations are event-driven and because of this, they are very easy on servers - they fire when – AND ONLY WHEN – something actually changed. Compared with polling integrations, this is a minute fraction of the largely present integration model banging on Airtable today.

In fact, Airtable should be paying users to switch to internally-driven event-based automations.

If Airtable wants to encourage the community to continue to build heavy-handed polling architectures for data interchange they will continue to sustain automation caps.


I agree that this is a great question. I also agree that it would be great to be able to purchase more automation runs.

However, automations is still relatively new, and I suspect that these things take time to roll out.

@Bill.French, while I agree with you about automations within Airtable being less resource intensive versus the glu-factory integrations, I think that a lot of people are creating automations for things that they were not using glu-factories for, things that were not automated before at all.

Running out of automations is yet another factor that people need to take into account when making decisions about using an automation script versus using script app. There are no run limits on when using script app.

1 Like

Good point. And it’s likely that the vast world of polling processes are not going to be recast with event-driven replacements for some time. But, this is on Airtable; they should have addressed this ages ago. So today …

Should they constrain new innovation by making it guesswork for customers if a new and innovative use of event automation will be (a) sustainable, and (b) affordable?

In my view, the past should not compromise Airtable’s ability to create competitive distance and the customer’s inability to assess or predict whether or not their innovations will fit a given budget.

Another dimension of this is in-platform and out-of-platform calls. Amazon is very clever about data movement across its network boundaries with far more expensive rates when data leaves their data center. They make it almost zero cost to perform compute operations inside the AWS domain. Other PaaS providers (like Airtable) should embrace this approach or force all of us to subsidize the bandwidth costs associated with the few customers who move data into and out of the Airtable realm.

Indeed, but this is a metric that few - even experienced developers - can easily predict. As such, it’s like building a leasing model where you are charged based on the number of times the engine’s cylinders actually fire. We don’t do that to consumers because they would never be able to relate to this metric. Instead, we use something relatable - like miles.

I set up automations to test various options and ran out (free plan) now I know what will be best for me I can’t implement it until the next billing period and I can’t find out my date to know when that is.
I like automations but will be conservative in using them

Indeed; same here. The outcome from an automation that fails because of a quota breach is no different than a SaaS platform that is down. And there’s no way to anticipate such “outage” and gracefully fail and recover.