# Understanding usage: Event streams

Workato measures Event streams usage in Events processed. Events generated through the Event streams API, or from workflow or API recipes, contribute to Events processed.

Event streams usage is counted in addition to Business actions or API calls when executed within workflow or API recipes.

# Usage calculation rules

Events streams usage calculations follow the general usage calculations rules, where successfully executed events count towards usage and failed actions are excluded.

Workato uses the following additional rules to calculate Events processed:

Only published events count toward usage. Consumed messages don't. Since Event stream triggers only consume messages, they don't contribute to Events processed.
API calls to the publish and batch publish endpoints of the Event streams API count as Events processed.

# Usage counting

The total Events processed for a job is the sum of all Events processed as part of the job. The total usage of a recipe workflow job that includes Events streams is the total Business actions + total Events processed. Similarly, the total usage for an API recipe job that includes Event streams is the API call + total Events processed.

Event streams actions don't contribute to Business actions.

# Example usage calculations

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

# Messages consumed (triggers)

# Usage totals

Total usage per job:

Business actions: 1
Events processed: 0
Total usage per job: 1 Business action, 0 Events processed

# Publishing messages (actions)

# Usage totals

Total usage per job:

Business actions: 2
Events processed: 1
Total usage per job: 2 Business actions, 1 Event processed

# Failed event in a workflow recipe

# Usage totals

Business actions: 4
Events processed: 0
Total usage per job: 4 Business actions, 0 Events processed

# Event streams in an API recipe

# Usage totals

API calls: 1
Events processed: 1
Total usage per job: 1 API call, 1 Event processed

# Event streams API

The following table demonstrates how Workato calculates usage for calls made through the Event streams API. This applies to both public and developer Event streams APIs.

Endpoint	Description	Messages consumed/published	Total usage
Consume endpoint	Doesn't contribute to Events processed.	35 messages consumed individually A batch of 50 messages consumed	0 Events processed
Publish endpoint	Contributes to Events processed. Each message counts as 1 Event processed.	28 messages published individually	28 Events processed
Batch publish endpoint	Contributes to Events processed. Each message counts as 1 Event processed.	100 messages published as part of first batch 100 messages published as part of second batch 66 messages published as part of third batch	266 Events processed
Multiple endpoints	Sum of all Events processed for a topic.	250 messages published using the publish endpoint 100 messages published using the batch publish endpoint 208 messages consumed using the consume endpoint Attempted publishing 20 messages using the batch publish endpoint that failed	558 Events processed

Last updated: 8/13/2025, 4:56:39 PM