Help Center

Run credits and AI credits for automations

Automations use two kinds of credit. Every run uses one run credit, and steps that ask AI to do something also use AI credits. Both come from monthly pools that belong to your workspace and are shared by all the apps in it.

Run credits

Your workspace gets a pool of run credits each month. Two things use them:

• An automation run uses one run credit, whatever started it and however many steps it has.
• An action in a connected app, such as posting to Slack, uses one run credit each time it runs.

A dry run does not use a run credit.

How many you get

The comparison table on the pricing page lists automation runs per month for each plan:

• Starter: 25,000
• Business: 100,000
• Agency and Enterprise: 500,000

The run credit pool you see in the Hub is a little larger than that figure, because it also includes your plan's allowance for actions in connected apps. Automations are not part of the Free plan.

The pool refills every 30 days, at the same time as your AI credits. Unused run credits from the monthly pool do not carry over.

See what is left

1. Open the Hub.
2. Open Billing, then Credits & usage.

The Run credits meter shows how much of this month's pool has been used.

To see which automations are using them, open Tools in your app, choose Automations and open the Runs tab. If one automation produces most of the runs, that is the one to tune.

If you run out

When the pool is empty, automation runs and connected-app actions are refused, and the run fails with a message saying you are out of run credits. Nothing is deleted and your automations stay as they are. You have three options:

• Buy more. On Credits & usage, use Buy run credits. Purchased run credits are added to your workspace's pool straight away.
• Move to a plan with a larger pool.
• Wait for the monthly refill.

Use fewer run credits

Schedules add up quickly. An automation that runs every 15 minutes uses 96 run credits a day, which is about 2,900 a month. An automation triggered by record updates on a busy table can use more than that.

• Run a schedule less often if hourly or daily would do.
• Use a more specific trigger. "On record created" fires far less often than "on record updated".
• Ask the assistant to add a condition early in the automation, so runs with nothing to do stop before they call a connected app.

AI credits

A step that asks AI to write, summarize, classify or decide something uses AI credits from your workspace's AI credit pool. This is the same pool the assistant and your AI agents use. If the pool is empty, the AI step is refused and the run reports the error.

Steps that do not use AI (reading and writing records, sending email, conditions and loops) do not use AI credits.