Automations billing

Learn how automations credits are consumed and billed.

ON THIS PAGE

This guide walks through how billing works for automations, helping you manage your credits effectively as you streamline your processes.

What is a credit?

Credits are the currency used to measure the resource consumption of your workflows. Most workflow blocks consume a credit when run.

How many credits does my plan include?

Each subscription plan comes with a set amount of credits.

  • Free Plan: 100 credits

  • Plus Plan: 1000 credits

  • Pro Plan: 2500 credits

  • Enterprise Plan: 5000 credits

Purchasing additional credits

Should you exhaust your monthly allocation, admins have the option to purchase additional credits to keep your workflows running smoothly. Simply navigate to the Billing page of your account, where admins can view your credit consumption and buy more credits as needed.

When do my credits renew?

For monthly plans, your credits will renew when your next billing charge occurs.

For annual plans, your credits will renew every month on the same date as your plan’s billing date. For example, if your plan renews on June 13th, your credits will renew on the 13th of every month.

How do workflow blocks consume credits?

A run is initiated whenever a workflow is triggered to execute. It encompasses the journey from the trigger point through to the final action block within your workflow. Each run's credit cost is determined by the blocks executed. You can view specific runs with the run viewer.

Credits are consumed as blocks are executed. However, not all blocks consume billable credits.

  • Triggers: These are the first step of any run and do not charge credits.

  • Conditional blocks: When Filter, If / else, and Switch are the last block executed in a run, they cost nothing. This will happen when the run matches a condition that has no deeper path associated with it.

  • Research record block: Each question asked in a Research record block costs 10 credits each time it executes.

  • Every other block: Every other block executed in a run costs 1 credit each.

⁠Should a block fail during execution due to a setup error or bug, any credit spent on it is refunded back.