Skip to main content

Automation usage

See how many actions your organization has used and how many are left in the Automation Center, and learn how Tape counts the actions that automations use.

Written by Leo

Actions are the unit that Tape counts when automations run. Automations use actions from your organization's quota. The usage view shows how many actions you've used and how many are available. It's meant to help you see early if your automations need more actions than you have.

Home in the Automation Center with the tiles Automations, Runs, Actions, and Saved hours. The Usage section at the bottom is highlighted. It shows a bar with Used actions and Available actions.

You can use the usage view for many things, including:

  • Checking how much of this month's actions your team has used.

  • Comparing this month's usage with last month's.

Note:

  • Usage is counted for the whole organization. All workspaces and apps share the same actions.

  • A single run can use up to 1,000 actions. Learn more about limits →

Who can see the usage?

  • Automations are available on the Free, Plus, and Premium plans. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • The usage is on Home in the Automation Center. To open it, you need to be an Organization admin or Organization owner and a Workspace admin in at least one workspace. Everyone who can open it sees the same usage for the whole organization. Learn more about the Automation Center →

See your usage

To check your usage:

  1. Select Automations in your sidebar. The Automation Center opens on Home.

  2. Find the Usage section.

  3. Hover over Used actions to see how many actions you've used, for example "1 action (1%)".

  4. Hover over Available actions to see how many are left, with the percentage.

  5. To compare months, switch the period at the top of Home between Current Month and Last Month. The period also applies to Usage.

Usage on Home in the Automation Center: hovering over Used actions and Available actions shows the number of actions with the percentage, and switching the period from Current Month to Last Month updates the tiles and Usage

Home also shows the number of runs and the Saved hours. Under Runs, you can see every run and filter by Status, including Throttled.

How actions are counted

Every run uses actions from your quota. The number depends on what the run does:

  • A run can use up to 1,000 actions. Then it fails with an error.

  • Each request a run makes to Tape or to another service uses one action. The trigger and filters don't use actions.

  • For example, Update record, Add comment, Send email, and Send HTTP request use one action each.

  • Actions on collected records, such as Update collected, use one action per record.

  • Perform calculation, Conditional actions, Filter collected, and Sort collected don't use actions.

  • Each pass of a loop uses actions again.

  • Manual runs use actions like any other run.

  • Simulated runs don't change data or send emails, so those steps don't use actions. Steps that read data, such as Search for records or Get view, still use actions. Requests to other services, for example with Send HTTP request or in Execute script, are sent for real in a simulated run and use actions too.

Tip: A loop repeats its steps for every record, so it can use many actions. Filter your list before the loop, so it only repeats for the records that need it.

When you run out of actions

The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page. If your organization needs more actions, upgrade your plan. Learn more about changing your plan →

If automations cause a lot of activity in a short time, Tape can throttle your organization until the load drops again. Learn more about throttling →

Let's look at an example

Let's say your recruiting team has an automation that sends one email per candidate with a loop over 100 candidates. Here's how to reduce usage:

  1. Open Automations → Home and check Used actions.

  2. Open the automation and add Filter collected before the emails, so only candidates with the status Interview get an email.

  3. Select Save changes.

Send email to collected uses one action per email, the same as a loop with Send email. It's easier to set up, but it doesn't use fewer actions. To use fewer actions, send fewer emails.

Usage errors

  • The usage is different from what you expect. The usage counts finished runs up to now. Runs that are still running are added when they finish.

  • Used actions look high. Open Runs and filter by Automation to find the automation that runs most often, for example one with the trigger When a record is updated that runs on every change. Add a filter so it only runs when needed.

  • Automations are delayed. Your organization may be throttled. Learn more about delayed automations →

Learn more

FAQs

Does a failed run use actions?

Yes. A failed run uses the actions it performed before it failed.

Can I see the remaining actions inside an automation?

No. There's no variable for the actions you have left this month. Check Used actions and Available actions in the Automation Center.

Can I see usage of each automation?

No, the Automation Center doesn't show the number of actions per automation or per run. Home shows the total for your organization.

When does the monthly quota reset?

The count starts again on the first day of each calendar month.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Automation usage report in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?