Make.com Array Aggregator Tutorial: Examples and Automation Guide for 2026

Make.com Array Aggregator is a flow-control tool for turning multiple bundles into structured array data. If your automation receives many rows, records, files, leads, or other bundles and a later step needs them together, the Array Aggregator can collect the values you choose into one aggregated output. This Make.com Array Aggregator Tutorial explains how the module works step by step, including source modules, mapping, Group By, target structures, testing, Iterator differences, troubleshooting, and real-world automation examples. If you are completely new to the platform, start with our Make.com Tutorial for Beginners 2026 before continuing with this guide.

What Is the Make.com Array Aggregator?

An aggregator in Make merges several bundles into a single bundle. According to the official Make Aggregator documentation, an aggregator accumulates bundles from a source operation and produces an aggregated output. The Array Aggregator is useful when you want to collect selected data from multiple bundles into an array structure.

How the Make.com Array Aggregator Works

The Make.com Array Aggregator waits for multiple bundles from a defined source section, then combines selected values into an array that can be mapped into a later module. The source module tells Make where collection starts, while the Array Aggregator settings determine which fields are included in the final array.

A typical pattern is: source module → multiple bundles → Array Aggregator → one structured array → destination module. This is useful when a later app or API expects a list of items in one operation instead of one bundle at a time.

How Does the Make.com Array Aggregator Work?

The aggregator accumulates bundles from the source section during an execution and produces output based on your configuration. The Source Module tells Make where aggregation begins. When Group By is used, distinct grouping values can produce separate grouped output bundles. Make’s official tools documentation also explains the roles of aggregators and iterators in data transformation.

If you’re deciding between an Iterator and an Array Aggregator, see our Make.com Iterator vs Array Aggregator guide for a practical comparison of arrays, bundles, filtering, and aggregation.

Source Module and Target Structure in Make.com Array Aggregator

The Source Module is the module whose bundles should be collected. Choose the point in the scenario that produces the repeated items you want to aggregate. Selecting the wrong source can cause missing data or unexpected output.

The Target Structure Type controls the shape of the aggregated array when a destination module expects a specific structure. When available, choose the structure that matches the next module so Make can expose the correct fields for mapping.

Make.com Array Aggregator Example: Combine Multiple Bundles Into One Array

A common Make.com Array Aggregator use case is combining several incoming bundles into one structured array before sending the data to another app or API.

For example, if three bundles contain these records:

{"name":"Ali","email":"ali@example.com"}
{"name":"John","email":"john@example.com"}
{"name":"Sarah","email":"sarah@example.com"}

the Array Aggregator can collect the selected values into one array-style output:

[
  {"name":"Ali","email":"ali@example.com"},
  {"name":"John","email":"john@example.com"},
  {"name":"Sarah","email":"sarah@example.com"}
]

This is especially useful when a destination expects one request containing multiple items instead of receiving one bundle at a time. If your automation works with JSON payloads, see our Make.com JSON Tutorial. If the aggregated array will be sent to an external API, our Make.com HTTP Module Tutorial explains how to build and send API requests.

How to Use Group By in Make.com Array Aggregator

Group By lets you create separate aggregated outputs for different grouping values. For example, orders can be grouped by customer, category, status, country, or another mapped field instead of combining every bundle into one array.

Use Group By only when the destination needs separate collections. If all incoming bundles should be combined into one array, leave grouping out and keep the configuration simpler.

Step 1: Create a New Scenario for the Make.com Array Aggregator

Create a new scenario in Make. This is the workspace where you connect modules and control how data moves between apps. Start with an empty scenario; we will add the source first and the Array Aggregator immediately after it.

Step 2: Add a Source Module for the Make.com Array Aggregator

The Array Aggregator needs bundles to combine. Choose a source that can produce multiple bundles, such as a search, iterator, or spreadsheet module. In this example, Google Sheets provides rows that can be collected into a structured array. Make’s guide to module types is useful if you want to understand the difference between triggers, searches, actions, and other modules.

Step 3: Add the Make.com Array Aggregator Module

Click the plus button after your source and add Array Aggregator. Its job is to collect multiple incoming bundles and build an array from selected fields. This is the opposite direction of an Iterator, which splits an array into separate bundles.

Step 4: Configure the Make.com Array Aggregator

Select the correct Source Module, define the target structure, and map the fields you need later. If you need Name, Email, and Company downstream, include those values in the aggregator. Group By is optional and is useful when you want separate aggregated results for distinct values such as Company.

Step 5: Add a Destination Module and Map the Aggregated Data

Connect the module that should receive the result. This may be an HTTP request, CRM, database, JSON workflow, or another compatible app. Map the Array Aggregator output to the destination field and make sure the structure matches what that destination expects. For another practical data-transfer workflow, see our Make.com Webhook Tutorial with ChatGPT and Google Sheets.

Step 6: Run the Scenario and Check the Make.com Array Aggregator Output

Use Run once with a small sample. Inspect the Array Aggregator output and verify that the expected records and fields are present. Then check that the destination receives the structure correctly before turning the scenario on.

Iterator vs Make.com Array Aggregator: Key Differences

Use an Iterator when you have an array and need to process each item separately. Use an Array Aggregator when multiple bundles need to be collected into an array. Advanced workflows can use both: split data, process or filter each item, and then aggregate selected results again. For a complete practical explanation of the opposite process, read our Make.com Iterator Tutorial. If you need to keep only selected bundles before aggregation, our Make.com Filters Tutorial shows how to control which data continues through a route.

Advanced Make.com Array Aggregator Settings

Group By can separate incoming bundles by a distinct value and produce grouped outputs. The Stop processing after an empty aggregation option can stop the route when no bundles reach the aggregator. For maintainable scenarios, plan the final target structure first and aggregate only the fields the next module actually requires. For deeper technical details about Source Module, Group By, empty aggregation behavior, and access to fields after aggregation, refer to the Make Aggregator Help Center guide.

Common Make.com Array Aggregator Errors and How to Fix Them

If the result is empty, confirm that the source produced bundles and that filters did not remove them. If fields are missing, check the aggregator mapping. If you see unwanted nested arrays, verify whether the field being aggregated is already an array and consider using an Iterator first when individual items need processing.

Real-World Make.com Array Aggregator Examples

Lead collection: collect lead bundles and structure the fields required by a compatible CRM or bulk API. Daily reporting: gather records produced during a scenario run and aggregate the values needed for a report or summary. Grouped summaries: group records by company, category, salesperson, or department before sending each grouped result to the next stage. Processed data: use an Iterator to process individual items and then an Array Aggregator to rebuild selected results into a new array.

Make.com Array Aggregator Best Practices for Reliable Workflows

• Test with two or three predictable records before scaling.
• Select the correct Source Module.
• Map every field you will need after aggregation.
• Filter unnecessary bundles before aggregation when appropriate.
• Use Group By only when you need separate grouped results.
• Inspect the aggregator output before sending it to an API or business app.
• Match the final array structure to the destination module’s requirements.

Frequently Asked Questions About the Make.com Array Aggregator

How do I aggregate multiple bundles into an array in Make.com?

Add an Array Aggregator after the modules that produce the bundles, select the correct Source Module, choose the fields you want in the aggregated output, and run the scenario. Make.com will collect the incoming bundles and produce an array structure that can be mapped into the next module.

What does the Make.com Array Aggregator do?

It collects multiple bundles and creates structured array data in an aggregated output. The exact fields and structure depend on the configuration you choose.

What is the difference between Iterator and Array Aggregator in Make?

An Iterator converts an array into separate bundles so items can be processed individually. An Array Aggregator works in the opposite direction by collecting multiple bundles into an array.

What does Group By do?

Group By evaluates a value for each incoming bundle and separates aggregation by distinct values. This is useful for grouping records by company, category, department, or another key.

Why are fields missing after the Array Aggregator?

A common reason is that the fields were not included in the aggregator’s configured output. Include the values you will need in modules that appear after the aggregator.

Can I use the Array Aggregator with an HTTP request?

Yes. If the receiving API expects a compatible array or bulk structure, build the required structure and map it into the request body.

Conclusion: Master the Make.com Array Aggregator

The Make.com Array Aggregator becomes straightforward once you remember the data direction: multiple bundles go in and structured aggregated data comes out. Start with a simple source, map only the fields you need, inspect the output, and then move into Group By, API payloads, reports, and more advanced automation workflows. Continue building your Make.com skills with our complete Make.com beginner guide, Make.com Iterator Tutorial, Make.com JSON Tutorial, and Make.com Webhook automation tutorial.