Split In Batches Advanced

Split data into batches and iterate over each batch

Overview

The Split In Batches Advanced node is designed to divide incoming data into smaller groups ("batches") and process each batch separately. This is useful when you need to handle large datasets in manageable chunks, such as sending emails in groups, processing records in limited-size sets, or integrating with APIs that have request size limits. The node offers advanced options like running batches in subworkflows, combining results, and controlling batch behavior during manual executions.

Practical examples:

Sending notifications to users in groups of 50.
Processing a large CSV file in parts to avoid memory issues.
Making API calls in batches to comply with rate limits.

Properties

Name	Meaning
You may not need this node — n8n nodes automatically run once for each input item. More info	Informational notice about n8n's default looping behavior.
Batch Size	The number of items to return with each call (minimum value: 1).
Options	Collection of additional settings:
• Reset	Whether the node will be reset and so with the current input-data newly initialized.
• Combine	Whether the node will combine all items before outputting to Done.
• Max Manual Batches	Maximum number of batches when doing a manual execution.
• Process Batch in Subworkflow	Whether the node will process the batches in separate Subworkflows.
• Clear Data Before Returning From Subworkflow	Whether the node will return an empty item after processing the data in the subworkflow.

Output

Loop Output: Each batch is outputted on the "Loop" output. Each item in the batch includes a pairedItem field indicating its index within the batch.
Done Output: When all batches are processed, the combined or final set of items is outputted here. If "Combine" is enabled, all items are merged before outputting. If "Clear Data Before Returning From Subworkflow" is enabled, an empty item ({json: {}}) is returned after subworkflow processing.
Binary Data: Not directly handled; output is structured as JSON objects.

Dependencies

No external services or API keys required.
Optionally uses n8n's internal API if "Process Batch in Subworkflow" is enabled.

Troubleshooting

Common Issues:

No output on Loop: Ensure your input data has enough items to form at least one batch based on the "Batch Size".
Unexpected empty output: If "Clear Data Before Returning From Subworkflow" is enabled, the node intentionally returns an empty item after subworkflow processing.
Too many batches in manual mode: Adjust "Max Manual Batches" to limit the number of batches during manual execution.

Error Messages:

Errors related to subworkflow execution may occur if the workflow is misconfigured or missing.
If "Batch Size" is less than 1, the node may throw a validation error.