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 event
• Write row
• Write cell

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 Google API supports batching 100 requests at a time.

The Google API doesn't support batching calendar update requests or send email requests.