How to Loop Over Items in n8n (and When You Do Not Need To)

Beginners often add a loop when n8n would already have handled the list for them. Knowing the difference saves time.

Most nodes already loop

If a node receives ten items, it normally runs once for each. You do not need a loop to send ten emails from ten rows.

When you need Loop Over Items

Use Loop Over Items (also called batching) when:

• an API allows only a few requests per second,
• you want to process in small groups,
• a later step must finish for one item before the next starts.

Basic pattern

1. Loop Over Items splits the list into batches.
2. Your processing nodes run for each batch.
3. A Wait node adds a pause if the API needs it.
4. The flow returns to the loop until all batches are done.

Common mistakes

• Forgetting to connect the “done” output to what happens afterwards.
• Making an endless loop by feeding the output back wrongly.
• Looping when the node could handle all items by itself.

Large data

Very large lists can use a lot of memory. Process in smaller batches or in a separate sub-workflow: sub-workflows.

Related

Rate limits are covered in the HTTP Request guide.

Quick answers

Do I need a loop to process many items?

Usually not, because most nodes run once per item automatically.

When is Loop Over Items useful?

For batching, rate limits or when each item must finish before the next.

How do I avoid hitting API limits?

Use smaller batches and a Wait node between them.

---

Related reading

• How to Build Your First n8n Workflow: Form to Sheet to Email
• n8n Webhook Node: Test URL vs Production URL Explained
• How to Use the HTTP Request Node in n8n to Call Any API