DocumentationWorkflowsLogic and data
Merge lists node
Merges two lists. Imported comparisons can pass on only the entries missing from the other list. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Merges two lists. Imported comparisons can pass on only the entries missing from the other list.
Use Merge lists as a clearly defined step in an anymize workflow.
- Processes 2 inputs.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Merge lists from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Merge lists has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Import contract | Configure this value in the node panel. | Standard |
| Import version | Configure this value in the node panel. | Standard |
| Match fields | Pairs fields from list 1 and list 2. All field pairs in use must match. For repeated field names on the right, the last pair applies. | Standard |
| New entries from | Passes on only entries from this list that have no matching entry in the other list. | Standard |
| Treat dots as part of the name | Reads customer.name as one complete field name. When off, it reads name inside customer. | Standard |
| Matching entries in list 2 | With only the first match, other equal entries from list 2 may be returned as new. This setting is retained from the original. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| List 1 | Configure this value in the node panel. | json |
| List 2 | Configure this value in the node panel. | json |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"input": "value"
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.