Merging http requests results in multiple subsequent executions

I’m a n8noob and created my first ETL workflow merging 3 different http requests. I combine 3 payloads and run some code to modifying + combine the JSON. My assumption is the merge-node would only execute once but it repeats the subsequent workflow 3 separate times. Please forgive my lack of experience - I’m sure I’ve missed a simple step.

The blue box highlighted in the workflow always executes 3 times (apparently once for each http request):

There are no error messages, just the annoyance of multiple executions at the end of the workflow.

  • n8n version: 1.78.1
  • Database (default: SQLite): SQLLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Windows

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Here is a gif animation of the workflow execution triplicated at point of merge:
n8n_workflow_trippleExecution

That’s expected behavior using the default settings of the nodes - it appends all items, so each item will be processed afterwards. You can use different options in the Merge Node to combine items in different ways, or you can stuff all the items in an array using the Aggregate node, turning multiple items into one. But it really depends on what you need to do.

Thank you @bartv; i tried the aggregate node - in the end I notice it’s possible to chain http requests together; that turned out to solve the multiple-execution loop > it only runs once now…

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.