Two systems — merge the answers
Billing and shipping each contribute half the picture; Merge (combine by position) joins the two branches into one record before it moves on.
What’s inside
5 nodes — every type links to its full reference page.
| Step | Node | Type |
|---|---|---|
| Order id | Inject | input.inject |
| Billing lookup | Edit Fields (Set) | processing.set |
| Shipping lookup | Edit Fields (Set) | processing.set |
| Join answers | Merge | logic.merge |
| Order 360 | Console | utility.console |
Import it
- Studio → Import — paste the JSON below (or the URL
/docs/templates/two-systems-merge-the-answers.json). - Or ask the AI Copilot with the JSON pasted after the phrase:
import this workflow json into a new workflow named "Two systems — merge the answers" - Any credentials the nodes need are
${credential.…}references — add them once in Admin → Credentials and the template picks them up. Nothing secret ships in a template.
The workflow document (flowdrome.workflow.v1, 4 node types)
{
"schemaVersion": "flowdrome.workflow.v1",
"id": "",
"name": "Two systems — merge the answers",
"version": "0",
"status": "draft",
"nodes": [
{
"id": "seed",
"type": "input.inject",
"label": "Order id",
"category": "trigger",
"config": {
"contentType": "application/json",
"payload": {
"orderId": "A-1002"
}
},
"position": {
"x": 0,
"y": 0
}
},
{
"id": "billing",
"type": "processing.set",
"label": "Billing lookup",
"category": "processing",
"config": {
"mode": "manual",
"assignments": [
{
"name": "invoice",
"type": "string",
"value": "INV-4402"
}
],
"include": "all",
"dotNotation": true,
"ignoreConversionErrors": false
},
"position": {
"x": 530,
"y": 0
}
},
{
"id": "shipping",
"type": "processing.set",
"label": "Shipping lookup",
"category": "processing",
"config": {
"mode": "manual",
"assignments": [
{
"name": "eta",
"type": "string",
"value": "Thursday"
}
],
"include": "all",
"dotNotation": true,
"ignoreConversionErrors": false
},
"position": {
"x": 530,
"y": 178
}
},
{
"id": "join",
"type": "logic.merge",
"label": "Join answers",
"category": "flow",
"config": {
"mode": "combine",
"combineBy": "combineByPosition",
"numberInputs": 2
},
"position": {
"x": 1060,
"y": 23
}
},
{
"id": "out",
"type": "utility.console",
"label": "Order 360",
"category": "utility",
"config": {
"message": "Full picture: {{ $json }}"
},
"position": {
"x": 1590,
"y": 23
}
}
],
"edges": [
{
"id": "e0",
"sourceNodeId": "seed",
"sourcePort": "output",
"targetNodeId": "billing",
"targetPort": "input"
},
{
"id": "e1",
"sourceNodeId": "seed",
"sourcePort": "output",
"targetNodeId": "shipping",
"targetPort": "input"
},
{
"id": "e2",
"sourceNodeId": "billing",
"sourcePort": "output",
"targetNodeId": "join",
"targetPort": "input1"
},
{
"id": "e3",
"sourceNodeId": "shipping",
"sourcePort": "output",
"targetNodeId": "join",
"targetPort": "input2"
},
{
"id": "e4",
"sourceNodeId": "join",
"sourcePort": "output",
"targetNodeId": "out",
"targetPort": "input"
}
],
"triggers": [
{
"id": "t0",
"nodeId": "seed"
}
],
"meta": {
"snippets": [],
"source": "template-gallery",
"description": "Billing and shipping each contribute half the picture; Merge (combine by position) joins the two branches into one record before it moves on."
}
} Generated from the verified demo corpus — this exact document seeds and runs on a fresh Flowdrome. Raw JSON: two-systems-merge-the-answers.json.