Event streams usage ​

Workato measures Event streams usage in Events. Event streams usage is added on top of the usage of the asset it runs in, such as a workflow recipe's Tasks, an API recipe's API Calls, or a skill's Tasks.

Some plans count publish steps as Tasks within your workflow usage instead of measuring them separately as Events. Additionally, Event streams API usage is non-billable on some plans. Refer to your contract or contact your Customer Success Representative for more information.

Event streams calculation rules ​

Event streams usage calculations follow the general usage calculation rules, where successful publishes count toward usage and failed actions are excluded.

Workato uses the following additional rules to calculate Events:

• Publishing counts as usage. Each published message counts as 1 Event. This applies whether the publish happens inside a recipe (or other asset) or through the publish and batch publish endpoints of the Event streams API.
• A batch publish counts each message. Each message in the batch counts as 1 Event.
• Failed publishes don't count. A publish that fails doesn't count as an Event. A publish that succeeds on retry counts.
• Consuming does not count as usage. Consumed messages, including messages received by an Event streams trigger or through the consume endpoint of the Event streams API, don't count as Events.

Event streams usage examples ​

The following examples demonstrate how Workato calculates usage for Event streams in different scenarios.

Messages consumed (triggers) ​

Published messages (actions) ​

Batch publish from a workflow recipe ​

Event streams in a Managed API recipe ​

Event streams in a skill invoked over MCP ​

Failed event in a workflow recipe ​

Event streams API ​

The following table demonstrates how Workato calculates usage for calls made through the Event streams API. Usage is calculated exactly as it is for the preceding asset-based scenarios: publishes count, consumes don't. This applies to both public and developer Event streams APIs.