How automation executions count against your plan

Every run that carries out its steps counts as one execution from your plan’s monthly balance when it ends. Runs refused by conditions, and practice runs, don’t count. When the balance runs out, new runs stop until the next month or until you buy a pack.

How it works

The balance is shared by the whole workspace, not per member.

One-time packs don’t raise the monthly limit. They add a balance that’s used after the monthly one runs out, and it carries over to the following months.

The usage bar updates live for the whole team, with up to a minute’s delay.

When the balance runs out

No new runs start from events or schedules, and the incoming webhook refuses requests. Including existing records stops.

Buy a pack or upgrade your plan from Your subscription: the trial, its states and read-only mode.

A real example