Understanding usage for product capabilities

Our usage strategy enables you to use a common billing unit for all of our capabilities. This approach lets you allocate resources based on your needs while maintaining pricing predictability and value.

Usage metrics rules

In general, all successfully executed operations contribute to overall usage and failed operations are excluded. Workato uses the following general rules to determine if an operation contributes to usage:

• Successful operations contribute to overall usage. Skipped actions due to conditional steps and control statements aren't included in the overall usage count.
• All rerun-eligible operations contribute to overall usage.
• Failed or canceled jobs count only the operations successfully executed before failure or cancellation.

Specific product capabilities have additional rules for calculating usage. Refer to the usage metrics for individual product capabilities for more information.

Usage counting

Workato applies the following logic to all usage calculations:

• Certain features are additive: Usage for certain features, such as IDP (Intelligent Document Processing) and Event streams, is calculated in addition to the primary usage metric of the recipe in which they occur. Similarly, Workato calculates usage for Workflow apps in addition to recipe usage.
• Usage is only counted once: Workato doesn't count product usage already calculated in another category. For example, IDP usage is measured in Pages processed, and IDP steps in a recipe aren't counted again as Business actions.

Usage metrics for product capabilities

Our usage-based pricing model tracks the usage of each of our product capabilities independently using market-standard usage metrics. At a high level, Workato employs the following usage metrics for each product capability:

Capability	Usage metric	Description
Workflows (recipes)	Business actions	Business actions are measured based on the trigger and action in an app steps within a recipe. The total Business action usage of a job is the sum of all eligible steps in the recipe.
API platform (Managed API and API Gateway)	API calls	API usage is assessed based on successful API requests. Individual recipe steps within API recipes aren't counted separately towards usage. API platform usage calculations apply to both Managed APIs (API recipes) and API Gateway (API Proxy), but at different ratios to credit.
IDP (Intelligent document processing)	Pages processed	Each page, whether standalone or part of a multi-page document, contributes to 1 Page processed. When IDP is used in a workflow, API, or Skill recipe, IDP usage is calculated in addition to the primary usage metric of the recipe.
Event streams	Events processed	Events processed in recipes and the Event streams API contribute to Event streams usage. Published messages count as as an Event processed, but messages consumed don’t count towards Event streams usage. When Event streams actions occur in a workflow, API, or Skill recipe, Event streams usage is calculated in addition to the primary usage metric of the recipe.
Recipe function/callable recipes	Business actions or API calls	Recipe functions and callable recipes inherit their usage type from the calling recipe at runtime.
MCP	MCP calls	MCP calls are the number of requests successfully processed by an API Collection configured as an MCP server. Both API Recipe Collections and API Proxy Collections can be configured as an MCP server.
Agent Studio	Genie actions	A Genie action is measured based on the number of prompts sent to a genie. Prompts can be sent by users or systems, such as another genie or App event. Each prompt counts as one Genie action.
Workato GO	GO seats	Workato GO usage is calculated based on the number of GO users.
Workflow apps	Workflow app seats	Workflow apps usage is calculated based on the number of Workflow app seats. Additionally, any recipe used by a Workflow app is also considered billable and contributes to overall usage, based on the type of recipe (workflow or API recipe).
Task	Tasks	A task is an action, step, or request taken in a workflow. Refer to your contract for more information.