Need help with pagenation loop for shopify order totals

Questions
1

I have spent 10+ hours beating my head against the wall for a shopify reporting workflow.

in a nutshell it pulls orders from a set date from shopify through http request, organizes them by tag and outputs it in a readable tag ie customer, wholesale, total etc.

the workflow WORKS, until theres more than 250 orders, thats the shopify limit with http request.

after that ive tried to add a pagenation loop, I DID THAT, i get the 9 or 10 pages / items in the loop and can verify all the data.

how do i merge the 10 items / pages to add up all the data?

i have tried accumulating, aggrigating, functions, merging, i cant get anything to work. ai taking me in circles. Any finger pointing in a direction would be helpful.

thanks in advance.

image
image2998×1104 301 KB

2
have spent 10+ hours beating my head against the wall for a shopify reporting workflow. in a nutshell it pulls orders from a set date from shopify through http request, organizes them by tag and outputs it in a readable tag ie customer, wholesale, total etc. the workflow WORKS, until theres more than 250 orders, thats the shopify limit with http request. after that ive tried to add a pagenation loop, I DID THAT, i get the 9 or 10 pages / items in the loop and can verify all the data. how do i merge the 10 items / pages to add up all the data? i have tried accumulating, aggrigating, functions, merging, i cant get anything to work. ai taking me in circles. Any finger pointing in a direction would be helpful. thanks in advance.

Based on the knowledge sources, you’re dealing with a pagination scenario where you need to combine data from multiple HTTP request pages. Here’s the solution:

Use the HTTP Request Node’s Built-in Pagination

First, I’d recommend using the HTTP Request node’s built-in pagination feature instead of manually creating a loop. This will automatically accumulate all pages for you:

  1. In your HTTP Request node, select Add Option > Pagination

  2. Set Pagination Mode to Update a Parameter in Each Request

  3. Configure the pagination parameters based on Shopify’s API (typically using a page or limit/offset parameter)

According to the documentation, with pagination enabled, “you end up with accumulated output of responses” automatically.

If You Must Use a Loop: Aggregate After the Loop

If you need to stick with your loop approach, the key is understanding where to place the Aggregate node. According to How to combine continuously incoming items into a list that come from a loop?:

If what you desire is to combine the results back into a single list after all the processing inside the loop is done, you need to use the Aggregate node instead of the “No Operation, do nothing” node that you have connected to the “Done” leg of the Loop Over Items. After all the items are processed they are spat out of the Done branch, and this is where you would aggregate them back into a single item.

Workflow Structure

Your workflow should look like this:

  1. Loop Over Items node (to handle pagination)

  2. HTTP Request node (inside the loop)

  3. Process/transform data (inside the loop)

  4. Connect back to Loop Over Items

  5. Aggregate node connected to the “Done” output of Loop Over Items ← This is the critical step

Configure the Aggregate Node

According to the Aggregate node documentation, use:

  • Aggregate: Select All Item Data

  • Put Output in Field: Enter a field name like allOrders

  • Include: Choose All fields to keep all your order data

This will combine all items from all loop iterations into a single item with all your data aggregated together.

Alternative: Use Code Node for Complex Accumulation

If you need more complex accumulation logic (like summing specific fields across pages), you can use a Code node after the loop’s “Done” output. As mentioned in Merge multiple runs into one, the Code node can merge data from multiple node executions.

The key insight is: don’t try to accumulate inside the loop - let the loop complete, then aggregate all items that come out of the “Done” branch.