Aggregator outputs multiple times instead of just once?

I’m trying to create a summary of a set of Google Calendar meetings that meet specific criteria. I’m using an Iterator to loop through the results of the Google Calendar search, filtering for the events I care about, creating some new variables based on event fields, and then trying to aggregate these across all events.

In the screenshot below, I’m retrieving 10 events, 3 of which pass the filters. I expect to see the Get Event Info (set multiple variables) node run 3 times, and maybe the Array Aggregator as well. But instead of outputting a single aggregated value, the array aggregator puts out 3 separate bundles, each of which get processed independently by the downstream node (another Set Variables node). Why? How do I get the Aggregator to wait until it has collected all the iterated values in an array, and then pass that array forward?

Hey there,

firstly - Search modules already produce a separate bundle for each item found, there is no need to iterate the output of the search module itself.

Second - you always aggregate the module producing the extra bundles. The Set multiple variables module is not creating extra bundles, only processing the existing ones. Change the source module to the Search module if you want to go back to one bundle.

Setting the Correct Aggregator Source

You need to set the “Source Module” field of the aggregator to where the bundles are coming from. This is usually an iterator module, but can also be a search/list/repeater module, or even the trigger module!

Combining Bundles Using Aggregators

Every result (item/record) from trigger/iterator/list/search/match modules will output a bundle. This can result in multiple bundles, which then trigger multiple operations in future modules (one operation per bundle). To “combine” multiple bundles into a single variable, you’ll need to use an aggregator of some sort.

Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and can apply to many use-cases like building of JSON, CSV, HTML.

You can find out more about the other types of aggregator modules here:

Question: Which is the best aggregator do you think you’ll need for your use-case?

Mapping a Specific Structure Into a Complex Field

If you have an array of collections, in programming terms, this is called an array of objects, or an array with non-primitive data types (“complex”).

The Array Aggregator module is very powerful because it allows you to build a new complex array of collections that matches a later module’s field to map multiple items (collections) to it. Such fields initially would allow you to manually add items, but you can toggle the “Map” switch to the “on” state and map a whole array into a single field.

This is done by selecting the “Target structure type” in an Array Aggregator module.

As you can see from the above example, the “Map” toggle on complex fields are used when you have an array variable (like from an array aggregator). Other combinations of modules may also allow you to generate an array that matches a future field’s array structure, like “Aggregate to JSON + Parse JSON”, or “Create JSON + Parse JSON”, but this is an advanced topic.

Question: Are you mapping your array into a field that accepts more than one item/collection?

Example

Here is an example of how your scenario could look like:

This is just an example. Your final solution may or may not look like this depending on your requirements and actual data.

For more information, see “Mapping with arrays” in the Help Centre. You should also do the Make Academy, which also covers the use of Iterators & Aggregators.

Hope this helps! Let me know if there are any further questions or issues.

@samliew