Batching API calls for performance improvements

Starting with version 2.5.5, we introduced batching capabilities for some activities. With batching, we write or send API calls from multiple activities into fewer calls, to increase runtime performance.

The following activities support batching:

• For each email
• For each file or folder
• For each row
• For each list item
• Write row
• Send email
• Create event
• Add list item
• Update single list item

How to optimize workflows with batching

To improve your workflows with batching, be aware of the following behavior.

If you want to use the output of an activity being batched (let's say, as a variable in another activity), a flush mechanism intervenes to retrieve the latest data and allow you to use it. The reason behind this behavior is that you cannot batch requests and consume their result immediately. Therefore, whenever you need to use the output of an activity being batched, a flush operation is performed.

Build your workflow so that you don't use output objects at each iteration, so that requests can be batched.

Limitations

The Microsoft 365 supports batching 20 requests at a time.

Batching is possible for Mail objects, but large attachments cannot be batched.