Automation is all about moving and transforming data efficiently. While n8n offers hundreds of integrations, its true power lies in how you handle the flow of data between nodes.
Three of the most powerful (but often overlooked) nodes are:
👉 Set – node is used to restructure data or to assign values to variables that can be reused in subsequent nodes within the current workflow.
👉 Split In Batches – for breaking data into smaller chunks
👉 Merge – for combining different data streams
This trio forms the backbone of advanced n8n workflows. In this guide, we'll explore what they are, when to use them, and how they work together, complete with real-world examples.
Prerequisites
Before diving in, make sure you have:
Basic knowledge of n8n workflows.
Familiarity with JSON data structures.
Hands-on experience with nodes like HTTP Request, Google Sheets, or Function node.

The Set Node
What is it?
The Set node allows you to define, restructure, or clean your data before passing it to the next step.
Where/Why/When to Use?
To map API fields (rename keys to match another system).
To add default values (e.g., set status = "pending").
To remove unnecessary fields and keep workflows clean.
How to Use?
Open the Set node → Add new fields manually or use expressions.
Choose which fields to keep, remove, or transform.
Real-World Example
Imagine you scraped leads from LinkedIn with firstName, lastName, and mail. Before sending them to a CRM API, you can use Set to restructure as:
{
"fullName": "{{ $json.firstName }} {{ $json.lastName }}",
"primaryEmail": "{{ $json.mail }}",
"status": "new"
}Pros & Cons
✅ Easy to restructure data
✅ Perfect for cleaning payloads
❌ Can get messy with large objects
The Split In Batches Node
What is it?
The Split In Batches node processes large datasets in smaller chunks, instead of sending everything at once.
Where/Why/When to Use?
Handling APIs with rate limits.
Breaking large Google Sheets exports into chunks.
Processing data step by step to avoid overload.
How to Use?
Set batch size (e.g., 10 items).
The workflow loops until all batches are processed.
Real-World Example
You fetch 100 contacts from Google Sheets. Instead of sending all 500 emails at once (risking API errors), you:
Use Split In Batches (10 per batch).
Send each batch via the Gmail node.
Continue until all contacts are processed.
Pros & Cons
✅ Prevents API quota issues
✅ Makes workflows more reliable
❌ Adds extra looping logic

The Merge Node
What is it?
The Merge node lets you combine two data streams in different ways.

Join the conversation! Your thoughts help the community grow.