Add Aggregators in Make.com

How to Add Aggregators in Make.com Scenarios

In make.com, aggregators let you collect multiple bundles of data into a single bundle so you can process them together in later modules. This step-by-step guide explains exactly how to add and configure aggregators to build more powerful automations.

What an Aggregator Does in Make.com

An aggregator in make.com gathers several input bundles and outputs a single bundle that contains a collection of those items. This is essential when you need to:

  • Combine multiple records into one summary
  • Build arrays or collections for later processing
  • Create reports, summaries, or grouped notifications
  • Reduce the number of operations on downstream modules

The aggregator always follows one or more modules that generate repeated output (multiple bundles). Its task is to merge those bundles into one structured data set.

Types of Aggregators Available in Make.com

When you add an aggregator in make.com, you will typically choose from several common options:

  • Array aggregator – turns multiple bundles into an array of items.
  • Text aggregator – concatenates text values from multiple bundles into one string.
  • Iterator + aggregator combination – used when you first need to break data apart with an iterator, then group the processed data again.

The exact names and availability of aggregator modules depend on the apps and tools you are using, but the configuration principles remain similar across make.com scenarios.

Before You Add an Aggregator in Make.com

To use an aggregator effectively in make.com, your scenario should already produce multiple bundles. Typical examples include:

  • A search module returning several records
  • A webhook receiving a list of items
  • A module that iterates through a list and outputs one bundle per item

If your scenario produces only one bundle, adding an aggregator will not provide a benefit. Confirm that the module immediately before the aggregator runs repeatedly and returns multiple bundles.

Step-by-Step: Add an Aggregator Module in Make.com

Use the following steps to insert an aggregator into your make.com scenario:

Step 1: Open Your Scenario in Make.com

  1. Sign in to your make.com account.
  2. Open the scenario where you want to group data.
  3. Make sure you can see at least one module that returns multiple bundles during execution.

Step 2: Insert the Aggregator Module

  1. Hover your mouse over the connection between the module that outputs multiple bundles and the next module.
  2. Click the small plus icon that appears on the connection line.
  3. In the module search dialog, type the name of the aggregator you need (for example, Array aggregator or another supported aggregator).
  4. Select the appropriate aggregator module to add it to your scenario.

The new module will now appear between the existing modules in your make.com workflow.

Step 3: Choose the Source Module and Fields

Most aggregator modules in make.com require you to choose which module to aggregate and which fields to include.

  1. Open the aggregator module settings by clicking its icon.
  2. In the Source module or similar field, select the module whose output bundles you want to group.
  3. Map the data fields from that module that you want to aggregate. This may include:
  • IDs, names, and titles
  • Numeric values to be summed or listed
  • Dates and timestamps
  • Text fields or messages

Each aggregator in make.com has its own mapping interface, but the core idea is to specify exactly which pieces of each bundle you want stored in the resulting collection.

Step 4: Configure Aggregation Settings

Depending on the aggregator type, you will see several configuration options, such as:

  • Grouping key – field used to group input bundles (for example, group all items by customer ID).
  • Delimiter – used by text aggregators to separate combined text values.
  • Maximum number of items – limit how many bundles are aggregated in a single run.
  • Order of items – ascending or descending order based on a selected field.

Set these options based on how you want the aggregated bundle to look and how downstream modules in make.com should consume it.

Using Aggregated Output Elsewhere in Make.com

Once the aggregator is configured, the module following it will receive a single bundle that contains a collection of items. Common use cases include:

  • Sending a single email digest that lists all items from the aggregated array.
  • Creating a single document (such as a PDF or spreadsheet) summarizing all collected data.
  • Storing aggregated data in a database record for reporting.
  • Posting a combined message into a chat app summarizing multiple events.

In the mapping panel of the next module, look for fields like Array, Collection, or Aggregated items. These will hold the data gathered by the aggregator module in make.com.

Testing and Troubleshooting Your Make.com Aggregator

After you add and configure the aggregator, test the scenario carefully:

  1. Run the scenario once with sample data and observe the execution inspector.
  2. Inspect the bundles produced by the source module to confirm there are multiple items.
  3. Open the aggregator output to verify that all expected items appear inside a single bundle.
  4. Check downstream modules to ensure they receive and process the aggregated data correctly.

If the aggregator is not behaving as expected in make.com, review these points:

  • Confirm that the correct source module is selected.
  • Verify the mapping of fields inside the aggregator.
  • Check any filters that might limit which bundles reach the aggregator.
  • Look for limits such as maximum number of items or grouping rules that might exclude some data.

Best Practices for Aggregators in Make.com

To keep your automations reliable and efficient, follow these best practices:

  • Limit bundle size – avoid creating extremely large collections that may slow down scenario execution.
  • Use clear naming – rename aggregator modules to reflect their purpose (for example, “Aggregate new orders by customer”).
  • Combine with filters – use filters before the aggregator to include only the bundles you actually want to group.
  • Document your mapping – keep notes or descriptions so others understand what data is being aggregated and why.

Where to Learn More About Make.com Aggregators

For additional details, screenshots, and the most up-to-date instructions on aggregators in make.com, review the official documentation at this guide to adding an aggregator.

If you need expert help designing complex scenarios, you can also explore consulting and implementation services at Consultevo, which specializes in automation and integration projects.

By understanding how aggregators work in make.com and following the steps above, you can transform many individual bundles into structured collections, making your automations more organized, efficient, and easier to maintain.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help

Leave a Comment

Your email address will not be published. Required fields are marked *