AutomationFlowsGeneral › Using the Merge Node - Merge by Key

Using the Merge Node - Merge by Key

Bymike @mikey on n8n.io

This is an example of how you can make Merge by Key work.

Manual trigger★★★★☆ complexity5 nodes
General Trigger: Manual Nodes: 5 Complexity: ★★★★☆ Added:

This workflow corresponds to n8n.io template #100 — we link there as the canonical source.

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json

  
Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

This is an example of how you can make Merge by Key work.

Source: https://n8n.io/workflows/100/ — original creator credit. Request a take-down →

More General workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

General

26 個 n8n 初學者小技巧,加速 5x 開發時間|🧠 省力知識庫. Manual trigger; 34 nodes.

General

NextCloud:NextCloud:Folder:create move copy delete list:File:upload move copy download delete. Uses start, nextCloud, readBinaryFile. Manual trigger; 28 nodes.

Start, Next Cloud, Read Binary File
General

Transporeon - orders - step 3 - process single. Uses start, functionItem, httpRequest, microsoftSql. Manual trigger; 26 nodes.

Start, Function Item, HTTP Request +3
General

This n8n workflow creates a complete recursive copy of any Google Drive folder, preserving the entire folder structure, all files, and sharing permissions. Duplicates folders with unlimited nested sub

Google Drive
General

Orbit:Member:upsert get update delete getAll lookup:Note:create update getAll:Activity:create getAll:Post:create getAll delete. Uses start, orbit. Manual trigger; 16 nodes.

Start, Orbit