Aggregating data with the Merge node
Configured with Code, Manual Trigger, Merge. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| On clicking 'execute' | Trigger | Manual Trigger | See node parameters |
| Ingredients in stock from recipe | Transform | Merge | See node parameters |
| Super Band | Transform | Merge | See node parameters |
| A. Ingredients Needed | Code | Code | See node parameters |
| B. Ingredients in stock | Code | Code | See node parameters |
| Merge recipe | Transform | Merge | See node parameters |
| A. Ingredients | Code | Code | See node parameters |
| B. Recipe quantities | Code | Code | See node parameters |
| A. Queen | Code | Code | See node parameters |
| B. Led Zeppelin | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
This will create a super band by merging Queen and Led Zeppelin
This will create a super band by merging Queen and Led Zeppelin
Similar to SQL Union All
(more flexible as not requires all fields to be the same)
Aggregating data with the Merge node
Aggregating data with the Merge node
Purpose and structure
This folder contains the Aggregating data with the Merge node workflow. Its executable nodes use code, manualTrigger, merge. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
On clicking 'execute'
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Manual/0228_Manual_Stickynote_Automate_Triggered.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- 3. Add items from B below items from A
- 1. Keep items from A if there's a match in B
- 2. Enrich items from A with matching data from B
- Aggregating data with the Merge node
- Adds the quantity needed to each ingredient in the recipe
- This will keep only the ingredients needed that are also in stock