Complex scenario: Iterator processes bundles correctly, but aggregator returns incomplete data

Questions
, , ,
1

:bullseye: What is your goal?

I’m building a Make.com scenario that receives customer order data through a webhook, processes multiple order items using an Iterator, checks inventory through an external REST API, routes the results based on stock availability, and then uses an Array Aggregator to combine everything into a single order summary before sending it to our CRM.

:thinking: What is the problem & what have you tried?

The webhook receives the order correctly and the Iterator also processes each item as expected. The inventory API returns the correct response for each bundle, and the Router correctly separates items that are in stock and out of stock.

The problem happens at the Aggregator stage. When the scenario reaches the Array Aggregator, some of the processed items are missing from the final array. In some executions, only the items from one Router route are included, while items processed through the other route are not included.

I’ve tried changing the Aggregator source module, checking the mapped fields, removing and recreating the Router filters, and running the scenario with different numbers of order items. I also checked the execution history and confirmed that the Iterator is generating all the expected bundles.

I’m not sure whether the issue is related to the Router branches, the Aggregator’s source module, or how Make handles bundles after branching. What would be the correct way to structure this scenario so that all processed items are reliably aggregated into one array?

:clipboard: Error messages or input/output bundles

There is no specific error message. The scenario completes successfully, but the final aggregated output contains fewer items than the Iterator processed.

For example:

Webhook → 5 order items
Iterator → 5 bundles
Inventory API → 5 responses
Router → 3 in-stock / 2 out-of-stock
Aggregator → only 3 items returned

I would appreciate any advice on how to correctly aggregate data coming from multiple Router branches.

3

Hey there,

Routers split the flow in separate paths. Items processed on one path are not directly available on another path. So an aggregator on path 3 will not have access to items existing in paths 1 and 2.

Depending on the exact flow, you can switch the router with an if/else + merge or use the make magic formula to retrieve the items before the aggregation happens.