Individual skill
n8n-loops-official
Use when working with multi-item data, batches, paginated APIs, rate-limited APIs, fan-out across multiple branches, anything that needs to "do this for each", or any time the user mentions looping, iterating, batching, paging, parallelism, or "loop over items". Triggers on "loop", "iterate", "for each", "batch", "page through", "paginate", "rate limit", "process all", "fan-out", "parallel branches", "concurrency", or any node that should run once vs once-per-item.
skills/n8n-loops-official/SKILL.md
Source commit 27b6b9f429ac0be90cae764512dbc579d7107e95
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 600
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- operations Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesSKILL.mdcore · 13,605 bytesreferences/HTTP_PAGINATION.mddoc · 9,649 bytesreferences/LOOP_OVER_ITEMS.mddoc · 12,290 bytes
Read excerpt
# n8n Loops
Three meanings of "loop" map to three mechanisms:
1. **"Run this node for every item."** Default. Most nodes loop automatically, so do nothing.
2. **"Run this node *once* with all items, not once per item."** The `executeOnce` setting (single boolean).
3. **"Process items in explicit batches with control flow between iterations."** The `Loop Over Items` node (formerly `Split In Batches`).
For paginated APIs, the HTTP Request node has built-in pagination. Almost always preferable to a hand-built page-counting loop.
## The model: items are an array
Data flows between nodes as an array of items, each `{ json: {...}, binary?: {...} }`. 50 items = 50-entry array.