Batch processing groups items into fixed-size chunks and works through them a chunk at a time, instead of one item at a time or all at once. It’s a practical way to balance speed against limits like rate limits or memory.
Example
Sending 10,000 emails in one uncontrolled burst is asking for trouble - a workflow might instead work through them in batches of 50, pausing briefly between batches so the email service doesn’t flag the activity or throttle the connection.
n8n relevance
n8n has a Split In Batches node - also called Loop Over Items - built for exactly this: it splits a long list into smaller groups and works through each one before moving to the next, often paired with a Wait node to add pacing. You’ll run into this pattern constantly with large contact lists, bulk data imports, or heavy API calls.
Related concepts
Related: rate limiting, idempotency, and node.