OBJECT_MERGER
OBJECT_MERGER node.
What it does
OBJECT_MERGER node.
Inputs & outputs
| Input handle |
|---|
| None |
| Output handle |
|---|
| None |
Configuration
No configuration.
Example
How it works
OBJECT_MERGER takes several named sub-objects from its input (identified by the objectKeys list in data) and shallow-merges their properties into a single output object written to data.outputKey. Each listed key must point to a plain (non-array) object; arrays and primitives are skipped. If two source objects share a key, the latter one wins and a debug log entry is written. Use it to combine the outputs of multiple upstream nodes into one payload before passing it to a send or database node.
Example
Scenario: A Workflow enriches a contact record by merging data from an HTTP_REQUEST (CRM data) and an LLM_COMPLETION (AI summary). Wire the HTTP response object and the LLM response object into the OBJECT_MERGER; set objectKeys: ["crmData", "aiSummary"] and outputKey: "enrichedContact". The merged object is then passed to an ADD_DATABASE_RECORD node in one step.