What problem does it solve?
This Skill prevents incorrect looping behavior in n8n workflows, especially when mixing per-item execution, one-time aggregation, batching, and paginated API fetching.
Core Features & Use Cases
- Execute-once vs per-item control: set
executeOnce: true for aggregates, totals, summaries, and notification/writes that must happen once per run.
- Pick the right looping mechanism: default per-item iteration vs
Loop Over Items for explicit batches, rate limits, polling, and stateful chunk processing.
- Use built-in HTTP pagination: fetch all pages with HTTP Request pagination instead of hand-rolled page loops.
- Avoid common wiring mistakes: correct understanding of
Loop Over Items outputs (done = output 0, loop = output 1), and guardrails for reset: true termination.
Quick Start
When your workflow needs to process each item and then send one final summary, keep the default per-item flow and set executeOnce: true only on the summary node.