How to Create Loop in n8n: The Complete 2026 Guide 🔄

Mastering how to Create Loop in n8n is the secret sauce that separates basic automations from professional-grade enterprise workflows. In the digital workspace of 2026, where data volumes have exploded, being able to iterate through thousands of records efficiently is no longer an optional skill; it is a necessity for any serious automation architect.

Understanding Loops in n8n: The Basics 💡

Think of a loop like a diligent barista in a busy coffee shop. If ten customers order lattes, the barista doesn’t build a new coffee machine for each person. Instead, they follow the same “brewing loop” ten times until everyone is caffeinated. In the context of automation, to Create Loop in n8n means telling your workflow to perform a specific action for every item in a list—be it rows in a Google Sheet, messages in Slack, or records from an API.

By default, n8n nodes operate on all items simultaneously (this is called “vectorized processing”). However, there are many scenarios where you need to process items one by one or in small chunks. This is where explicit looping comes into play, ensuring your API rate limits aren’t crushed and your logic remains sound.

Method 1: The “Split In Batches” Native Loop 🛠️

The “Split In Batches” node is the traditional way to Create Loop in n8n without writing a single line of code. It acts as a gatekeeper, taking a giant pile of items and letting them through in small, manageable groups.

When using this node, you connect the “loop” output back to an earlier part of your workflow. Once the batch is finished, the node checks if there are more items left. If yes, it goes again; if no, it finishes. It’s like a revolving door that only lets five people into a club at a time.

{
  "name": "Split In Batches Example",
  "nodes": [
    {
      "parameters": {
        "batchSize": 10,
        "options": {}
      },
      "type": "n8n-nodes-base.splitInBatches",
      "typeVersion": 3,
      "position": [250, 300]
    }
  ]
}

The JSON snippet above represents the configuration of a standard Split In Batches node. You simply define the batch size—usually set to 1 if you want a true one-by-one loop—and connect your logic in a circular fashion.

Method 2: High-Performance JavaScript Loops 🚀

For complex logic, you might want to Create Loop in n8n directly within a Code Node. This is significantly faster for data transformation tasks because it avoids the overhead of triggering multiple nodes repeatedly. In 2026, the n8n Code node is more powerful than ever, allowing for seamless integration of external libraries.

// This loop iterates through all incoming items and adds a "processedAt" timestamp.
// Think of this as a factory line where we stamp each box as it passes by.

const items = $input.all(); // Grab all incoming data items
const processedItems = [];

for (let i = 0; i < items.length; i++) {
  // We create a shallow copy of the JSON to avoid mutating the original input unexpectedly
  let itemData = { ...items[i].json };
  
  // Add our custom logic here
  itemData.processedAt = new Date().toISOString();
  itemData.status = "Automated_2026";
  
  // Push the modified data back into our results array
  processedItems.push({ json: itemData });
}

// Return the final array for the next node to consume
return processedItems;

This code iterates through every incoming item, adds a timestamp, and updates a status field. It is highly efficient because the entire "loop" happens within a single execution step of the Code Node, rather than cycling through the n8n canvas multiple times.

Native vs. Code Loops: Comparison Table 📊

Feature	Split In Batches (Native)	Code Node (JavaScript)
Ease of Use	High (No-code)	Medium (Requires JS knowledge)
Performance	Slower for large datasets	Extremely Fast
Visibility	Visual execution path	"Black box" logic
Rate Limiting	Excellent control	Difficult to manage within the loop

Pros and Cons of Different Looping Methods ⚖️

The Native Loop Approach

• ✅ Pro: Easy to debug because you can see each item passing through the canvas.
• ✅ Pro: Perfect for interacting with external APIs that have strict rate limits.
• ❌ Con: Can be slow if you are looping through 10,000+ items one by one.

The Code Node Approach

• ✅ Pro: Massive speed advantages for data cleaning and transformation.
• ✅ Pro: Allows for complex conditional logic that would be messy in a visual flow.
• ❌ Con: Harder for non-technical team members to maintain or understand.

How to Use It Properly: A Step-by-Step Guide 📝

To successfully Create Loop in n8n using the native method, follow these precise steps to avoid the dreaded "infinite loop" error.

1. Fetch your data: Use any node (like HTTP Request or Google Sheets) to bring data into the workflow.
2. Add the Split In Batches Node: Set your batch size (e.g., 1 to process items individually).
3. Build your logic: Connect the "loop" output to the nodes that perform the work (e.g., send an email).
4. Close the loop: Connect the output of your last "work" node back to the input of the Split In Batches node.
5. Handle Completion: Connect the "done" output of the Split In Batches node to whatever happens after the loop finishes.

Advanced Tips and Tricks 💡

When you Create Loop in n8n, performance tuning is key. If you are hitting API rate limits, don't just loop; add a Wait Node inside your loop. This acts like a "power nap" for your automation, giving the external server a second to breathe before the next request arrives.

Another pro tip: Use the Merge Node after a loop if you need to combine the results of the loop with data that didn't pass through the loop. This is essential for generating comprehensive reports at the end of an execution. For more technical details on node behavior, check out the official n8n documentation.

Frequently Asked Questions (FAQ) ❓

How many items can I loop through in n8n?

There is no hard limit, but performance depends on your hosting. If you are using n8n Cloud or a robust self-hosted Docker instance, you can Create Loop in n8n for tens of thousands of items, though the Code node is recommended for such volumes.

Can I nest loops within loops?

Yes, you can place a Split In Batches node inside the loop of another Split In Batches node. This is common when dealing with hierarchical data, like looping through "Departments" and then looping through "Employees" within each department.

What is the "no-op" node and why use it in loops?

The "No-Op" (Wait or Sticky Note) is often used to keep the visual flow clean or to provide a specific connection point when closing a complex loop. It ensures that the circular logic is clearly defined for the n8n engine.

Ready to take your automation skills to the next level? Explore more guides and tutorials at n8nnode.com.