I’ve got some iterators in my scenario, and I want to aggregate the output from them using an array aggregator. However, I want to do this multiple times from each iterator module to send the data to different routes.
The aggregation works, and I’m able to map the output from the iterator in each, but after a few modules, I’m not able to map those iterators in the Array aggregator. Images attached below. Is there a limit to how many aggregators can be used in a path or something? Or am I doing something wrong?
since module 23 is aggregating module 7, all the rest are inside that aggregation. So the following module can aggregate on them, cause they are already aggregated. Shouldn’t module 23 be aggregating module 20 though? Then the next one aggregate module 16 and so on to work their way backwards, with the last aggregator aggregating module 7? Same as it is on the other route.
So, the source module for the images aggregator[23] is Images Iterator[7]. While the source module for Planning Docs aggregator[31] should be planning docs iterator[13] as they both are using different data, and each aggregator has to aggregate a different type of data.
Are you saying aggregator[23] aggregates data from all the modules prior and I can use that as a source module for aggregator[31]? Cuz, that doesn’t make sense, especially when it’s all different data that’s being retrieved, so how does it differentiate?
No, all iterators are iterating different arrays coming from the custom webhook. Then I want each aggregator to aggregate that particular iteration, so I can send them as a complex array into different airtable fields.
I need complex arrays as these are attachments being sent to airtable.
Yeah, I had that, I was just wondering if this was possible or not as I was testing different methods to set up my scenario, to see which one would be the best. Since, I wanted to try and decrease the no. of modules. Guess, will have to create 4 sets for each path…
Seems like Make doesn’t let you aggregate into separate arrays in the same path, like @samliew has shown.