Describe the problem/error/question
The MERGE node with the Combine By Position does not work as expected.
Instead of combining the two inputs, it merely outputs the Input1 of the node.
The error picture is such:
INPUT1:
[
{
“output”: “DO-NOTHING”
},
{
“output”: “DO-NOTHING”
},
{
“output”: “DO-NOTHING”
},
{
“output”: “FORWARDING”
},
{
“output”: “DO-NOTHING”
}
]
INPUT2:
[
{
“from”: ""ClickUp Team" ",
“subject”: “Access GPT-4o, o1, and o3-mini in ClickUp—Half the Price”,
“attachment”: “false”,
“textPlain”: “MSG_BODY_1”
},
{
“from”: "AlphaSignal ",
“subject”: “
OpenAI Releases Speech Model APIs: Real-Time AI Voices & Transcription”,
“attachment”: “false”,
“textPlain”: “MSG_BODY_2”
},
{
“from”: ""ClickUp Team" ",
“subject”: “Try automatic scheduling”,
“attachment”: “false”,
“textPlain”: “MSG_BODY_3”
},
{
“from”: "Ulf Morys ",
“subject”: “Bittte morgen auf jeden Fall anrufen”,
“attachment”: “false”,
“textPlain”: “MSG_BODY_4”
},
{
“from”: "Medium ",
“subject”: “Samir Issa added your story A practical n8n workflow example from A to Z — Part 1: Use Case, Learning Journey and Setup to their list AI”,
“attachment”: “false”,
“textPlain”: “MSG_BODY_5”
}
]
I “just” want to join the “output” info from INPUT1 to each item in INPUT2 by position. In other workflows (but with different hosting) this worked fine by simply using the MERGE node and “combine by position”.
However, the output from the MERGE node is invariably simply the INPUT1, aka:
[
{
“output”: “DO-NOTHING”
},
{
“output”: “DO-NOTHING”
},
{
“output”: “DO-NOTHING”
},
{
“output”: “FORWARDING”
},
{
“output”: “DO-NOTHING”
}
]
What is the error message (if any)?
None, just an unexpected output.
Please share your workflow
Share the output returned by the last node
Information on your n8n setup
- n8n version: 1.83.2
environment:
DB_TYPE: postgresdb
DB_POSTGRESDB_HOST: postgres
DB_POSTGRESDB_PORT: 5432
DB_POSTGRESDB_DATABASE: ${POSTGRES_DB}
DB_POSTGRESDB_USER: ${POSTGRES_USER}
DB_POSTGRESDB_PASSWORD: ${SOFTWARE_PASSWORD}
EXECUTIONS_MODE: queue
QUEUE_BULL_REDIS_HOST: redis
QUEUE_HEALTH_CHECK_ACTIVE: “true”
WEBHOOK_TUNNEL_URL: https://${DOMAIN}
WEBHOOK_URL: https://${DOMAIN}
N8N_BASIC_AUTH_ACTIVE: “true”
N8N_BASIC_AUTH_USER: ${N8N_BASIC_AUTH_USER}
N8N_BASIC_AUTH_PASSWORD: ${SOFTWARE_PASSWORD}
N8N_HOST: ${DOMAIN}
N8N_EMAIL_MODE: “smtp”
N8N_SMTP_HOST: ${SMTP_HOST}
N8N_SMTP_PORT: ${SMTP_PORT}
N8N_SMTP_USER: " "
N8N_SMTP_PASS: " "
N8N_SMTP_SENDER: ${SMTP_FROM_EMAIL}
N8N_SMTP_SSL: “false”
NODE_TLS_REJECT_UNAUTHORIZED: 0
EXECUTIONS_DATA_PRUNE: ${EXECUTIONS_DATA_PRUNE}
EXECUTIONS_DATA_MAX_AGE: ${EXECUTIONS_DATA_MAX_AGE}
N8N_ENCRYPTION_KEY: ${N8N_ENCRYPTION_KEY}
N8N_DEFAULT_BINARY_DATA_MODE: filesystem
N8N_PAYLOAD_SIZE_MAX: 32
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE: “true”
links:- postgres
- redis
- Running n8n via (Docker, npm, n8n cloud, desktop app):: Running in elest.io instance
- Operating system: Managed service… very probably some kind of Linux
no problem, you have to feed the bird 
