Aggregator Running Multiple Times After Search Records Module

How To
,
1

Hi everyone,

I’m experiencing an issue in Make.com where my aggregator module is not merging all bundles as expected. Here’s my setup:

  • I have a Search Records module that outputs multiple bundles (one per record).
  • I want to merge all these bundles into a single aggregated bundle.
  • I placed the aggregator immediately after the Search Records module.
  • I’ve removed any grouping settings in the aggregator, expecting it to aggregate all incoming bundles into one.
  • However, the aggregator seems to be running multiple times, and I’m getting multiple aggregated bundles instead of a single one.

Has anyone encountered this issue before? How can I configure the aggregator to execute only once and merge all incoming bundles from the Search Records module into a single bundle?

Any advice or guidance would be greatly appreciated!

Thanks in advance,
Justin
blueprint (1).json (133.6 KB)

2

Hey there,

you always aggregate the module producing the extra bundles. In your case the Search Records module.

1 Like
3

Welcome to the Make community!

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!

867×340 53.2 KB

For more information, please refer to the Make Academy.

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:

Mapping a Specific Structure Into a Complex Field

The Array Aggregator module is very powerful because it allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.

This is done using the “Target structure type” field in an Array Aggregator module.

Here is an example:

1247×438 86.6 KB

As you can see, the “Map” toggle on complex fields are used when you have an array. You can easily build an array variable to map to a future module’s field, by using an Array Aggregator module and select the “Target Structure Type” as the future module’s field you have mapped the array into.

Example

Here is an example of how your scenario could look:

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

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

— @samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.