Automation

Using Make.com Iterator and Aggregator Effectively

Learn how to use Make.com Iterators and Aggregators for effective workflow automation.

4 min read

Learn how to use Make.com Iterators and Aggregators effectively to process dynamic arrays, automate workflows, and optimize operation costs.

Understanding Iterators and Arrays in Make.com

Iterators in Make.com are modules designed to manage arrays by splitting each array entry into separate bundles. Arrays are dynamic collections of data items such as strings, numbers, or objects, varying in size. Processing such arrays without iterators often results in handling only the first entry, leaving other entries untouched.

By using an iterator, you can ensure that every array entry is processed individually, enabling dynamic workflows that adapt to varying quantities of data.

prerequisites

  • Access to the Make.com platform.
  • Basic understanding of scenario/module configuration.
  • A use case involving datasets with multiple entries (e.g., an API returning arrays of items).

Step-by-Step Guide to Using Iterators in Make.com

Here's how to set up and use iterators effectively:

steps

  1. Add an Iterator Module

    • Open your Make.com scenario and insert the Iterator module.
    bash
    # Example: Iterator added from the "Tools" section in Make.com
  2. Select the Input Array

    • Configure the input for the Iterator module by selecting the array to split.
    bash
    # Example configuration: Choose "List Array" from dynamic inputs
  3. Test the Iterator Output

    • Run the scenario and inspect the Iterator module's output bundles.
    bash
    # Output: Bundles created, e.g., Bundle 1, Bundle 2, Bundles for every array entry
  4. Add Modules for Further Processing

    • Append additional modules to process each bundle dynamically, such as a "Google Sheets Add Row" module.
    bash
    # Example: Map bundle-specific data fields into subsequent modules

When to Use the Aggregator Module

Use an Aggregator when

  • You need to consolidate multiple processed bundles into a single entity.
  • Generating reports, invoices, or other outputs that summarize grouped data.
  • Minimizing costs for scenarios with high data volume by reducing operation counts.

Operation Cost Considerations

Example: Dynamic Weather Forecast Processing

This example retrieves and processes a 5-day weather forecast:

steps

  1. Retrieve Weather Data

    • Use an API module to fetch a 5-day forecast as an array.
  2. Split Forecasts with an Iterator

    • Add the Iterator module and select the forecast list.
  3. Process Individual Forecasts

    • Map dynamic fields from the Iterator into modules (e.g., add weather data to Google Sheets).
  4. Aggregate Summary Data

    • Append an Aggregator to combine processed weather data into a single text summary.

Common Mistakes and Debugging

FAQ

What is a Make.com Iterator used for?

A Make.com Iterator is used to divide arrays into individual bundles for dynamic processing, enabling workflows that adapt to variable quantities of data.

How does the Aggregator in Make.com help reduce costs?

The Aggregator consolidates multiple bundles into one, reducing the total operation count and thereby optimizing the cost-efficiency of scenarios with large datasets.

Can Iterators and Aggregators be combined in the same scenario?

Yes, Iterators help break down arrays into bundles for processing, while Aggregators reassemble the processed bundles. Using both ensures dynamic processing and consolidation.


Official reference: Make documentation.