Merge
The Merge node combines multiple JSON objects or arrays into a single unified structure. This is useful for aggregating data from multiple previous steps, combining API responses, or building composite payloads.
Actions
| Action | Description |
|---|---|
json:merge | Merge multiple JSON objects or arrays into one |
json:merge
Merges the selected inputs into one combined result. Use it when two or more earlier steps each have part of the information you need.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
inputs | array | Yes | The objects or lists you want to combine. These usually come from earlier steps. |
mode | string | No | Merge strategy: shallow, deep, concat. Defaults to shallow |
conflictResolution | string | No | How to handle key conflicts: lastWins, firstWins, error. Defaults to lastWins |
Merge Modes
- Shallow merges only the main fields. If two inputs have the same field, the later value can replace the earlier one.
- Deep merges main fields and nested details. Use this when the data has sections inside sections, such as customer details and address details.
- Concat joins multiple lists into one longer list.
Friendly Examples
Combine Customer Details
Use this when one step returns basic customer information and another step returns account information.
| Input | Example |
|---|---|
| Customer step | Name, email, phone |
| Account step | Account ID, plan, status |
| Merge result | One customer record with both contact and account details |
Combine Nested Details
Use this when each step returns a different part of the same record.
| Input | Example |
|---|---|
| Profile step | Customer name and address |
| Billing step | Billing contact and payment status |
| Merge result | One complete customer profile with profile and billing sections |
Join Two Lists
Use this when you have two lists that should become one.
| Input | Example |
|---|---|
| List 1 | Open tickets from email |
| List 2 | Open tickets from API |
| Merge result | One list of all open tickets |
Connection
No connection required. This is a data transformation node that operates on in-memory data.
Output
For list joining, the result is one combined list. For object merging, the result is one combined object that later steps can use.