Accumulate HTTP response results

[andereoliveira]

Hello all, this is my first question. I’ve tried multiple options but none worked.

I have the following workflow:

The HTTP returns a JSON with an items list and other things. I want to have all the items in the same object at the end of the workflow. I’ve asked ChatGPT and the better i came up with is the following snippet from “Update vars” node:

let accumulatedItems = $json.accumulatedItems || [];

console.log("accumulatedItems befores: ",accumulatedItems);


const currentItems = $json.items; 
accumulatedItems.push(...currentItems); 

console.log("accumulatedItems after: ",accumulatedItems);


return [
  {
    json: {
      accumulatedItems, 
      nextPage: $json["next_page"], 
    },
  },
];

But the accumulatedItems is always empty when node starts. Can you help me?

Thanks in advance and n8n is great!

[n8n]

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:

[ihortom]

Welcome to the community @andereoliveira !

Tip for sharing information

Pasting your n8n workflow

---

Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

That implies to any JSON output you would like to share with us.

Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!

---

I would advise engaging Loop node. The last node in the loop (the one that loops back to the Loop node) could bt Set node that contains only the data you need. Then once the loop iteration is completed, its “done” branch will have all the items created by the mentioned Set accumulated.

Also, you migth scrap that whole thing and utilise the built-in pagination feature of HTTP Request node if that is what you are trying to do with that loop in your screenshot. With pagination enabled you also end up with accumulated output of responses.

[andereoliveira]

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

WORKFLOW

I’ve tried the loop but since there was a message saying that probably i wont need it, and i as able to achieve the loop without it so i’ve removed it.

I saw that there is a pagination feature after the post, I’ll try it later.

Anyway, is there a way to store variables in the worklow scope instead of node scope?

[ihortom]

@andereoliveira

is there a way to store variables in the worklow scope instead of node scope?

Yes, but it is limited in fucntionality, getWorkflowStaticData | n8n Docs.

I still insist on pagination feature instead. Using static data in this case is not suitable.