Automation limits and what counts as an action
Counted per step, not per workflow run. The arithmetic surprises people, so here it is plainly.
One sentence causes most of the confusion here, so it is worth stating first: automation actions are counted per step, not per run.
A six-step workflow that runs a hundred times has used six hundred actions, not a hundred. Do that multiplication before you enable anything on a high-frequency trigger, because the difference between those two numbers is the difference between comfortable and out.
Steps
Know your allowance
5,000 automation actions a month on Starter, 35,000 on Pro, 125,000 on Growth and 300,000 on Scaler.
Count per step, not per run
Steps × trigger frequency. Write it down before enabling a workflow on something that happens hundreds of times a week.
Watch the meter
Automation runs appear on the Home capacity bars alongside AI voice minutes, AI messages and carrier minutes — showing what runs out first if volume keeps climbing.
Trim steps rather than workflows
A notify step nobody reads is pure cost. Removing it is cheaper than turning off a useful automation.
Narrow with "only if"
The cheapest optimisation available: a workflow firing on a tenth of the events costs a tenth as much, and is usually better behaved too.
Switch off what you are not using
A workflow that is off consumes nothing. Paused workflows nobody has looked at in months are free to keep and free to delete.
Check it worked
Add up the steps across your live workflows and multiply each by its run count from the list. That number should be close to your meter — and if it is not, some workflow is running far more often than you think.
The parts people get wrong
- AI messages sent by workflows also count against your separate AI message allowance.
- The run count shown against each workflow in the list is the easiest way to find your most expensive automation.