Powerful Make.com Iterator Tutorial: How to Process Multiple Items in 2026
Want to process multiple records automatically instead of handling them one by one? This Make.com Iterator Tutorial shows you how to work with arrays, split items into individual bundles, map data, test your workflow, and automate repetitive processing.
Make.com is a visual automation platform that lets you connect apps and move data between them without traditional coding. As your workflows become more advanced, you will eventually encounter lists or arrays containing multiple items. That is where the Make.com Iterator becomes useful.
In this step-by-step guide, we will use a visual example built around Google Sheets → Iterator → Airtable. You will learn what an Iterator does, how to configure it, how to map fields, how to test the scenario, and how to schedule the automation.
Important technical note: an Iterator is needed when the value you want to process is an array inside a bundle. Some Make search modules can already emit separate bundles, in which case adding another Iterator may not be necessary. The screenshots below are designed to demonstrate the Iterator workflow visually; always inspect the actual output of your source module before deciding whether an Iterator is required.
What Is the Make.com Iterator?
The Iterator is a built-in Make.com flow-control tool used to convert an array into separate bundles. Each item can then move through the following modules individually.
For example, imagine an earlier module returns three leads inside one array:
[
{"name":"Ali","email":"ali@example.com"},
{"name":"John","email":"john@example.com"},
{"name":"Sarah","email":"sarah@example.com"}
]The Iterator can split that array so the next module receives one lead at a time. This is useful for product lists, API results, order line items, contacts, attachments, content ideas, and many other automation jobs.
For Make’s own explanation, see the official Make Iterator documentation.
What You Will Build
Our visual workflow is:
Google Sheets → Iterator → Airtable
The goal is to retrieve source data, process individual items, and create separate records in Airtable. Before starting, prepare a Make.com account, a Google account, a test spreadsheet, and an Airtable base with suitable fields.
Step 1: Create a New Scenario in Make.com
Log in to Make.com and open your dashboard. Click Create a new scenario to open the visual scenario builder.
A scenario is the workspace where you connect apps and define the flow of information. Give the scenario a clear name so you can identify it later, for example Google Sheets – Iterator – Airtable.
Pro Tip: descriptive scenario names become increasingly important when you manage several automations.
Step 2: Add the Google Sheets Module
Click the + button, search for Google Sheets, and select the source action shown in the example.
Your source module is responsible for bringing data into the scenario. Use clear spreadsheet headers such as Name, Email, Company, Phone, and Status so field mapping remains easy to understand.
SEO example workflow: a lead sheet can contain many prospects that later need to be processed by your CRM or database automation.
Step 3: Add the Iterator Module
Click the next + button and search for Iterator. Add the Iterator from Make’s built-in tools.
This is the central module in our Make.com Iterator Tutorial. Its job is to take an array and output each array element as a separate bundle.
Conceptually, [Item 1, Item 2, Item 3] becomes Bundle 1, Bundle 2, Bundle 3. The module after the Iterator can then process each item independently.
Step 4: Add the Airtable Module
Click the + button after the Iterator, search for Airtable, and choose Create a Record.
Airtable is the destination in this example. Each item produced by the Iterator can be mapped into a new Airtable record.
Your workflow should now visually resemble Google Sheets → Iterator → Airtable.
Step 5: Configure the Google Sheets Module
Open the Google Sheets module, connect your Google account, select the correct spreadsheet and sheet, and configure the relevant source settings.
Make sure your data is clean and your headers are descriptive. Good source data reduces mapping errors later in the automation.
Common mistake: do not assume every source module returns an array. Run the module and inspect its output. If it already returns one bundle per row, an Iterator may be unnecessary. If it returns a genuine array that must be split, map that array in the next step.
Step 6: Configure the Iterator Module
Open the Iterator and locate the Array field. Map the actual array output from the previous module into this field.
Once the array is mapped correctly, Make can turn each element into a separate bundle for downstream processing.
If you cannot see the expected array: run the previous module once with sample data. This helps Make learn the output structure and can expose additional fields for mapping.
Step 7: Configure the Airtable Module
Open Airtable – Create a Record, connect your Airtable account, choose the correct Base and Table, and map the Iterator output into the matching Airtable fields.
| Iterator Output | Airtable Field |
|---|---|
| Name | Name |
| Company | Company |
| Phone | Phone |
| Status | Status |
Check every mapping carefully. A scenario can run successfully while still sending data to the wrong field.
Step 8: Test Your Scenario
Before activating the automation, click Run once and test the complete workflow with sample data.
Inspect the output from each module. Confirm that the source returns the expected information, the Iterator produces the expected bundles, and Airtable receives the correct records.
Also open Airtable and verify the real destination data. Check names, emails, companies, statuses, and any other mapped values.
Pro Tip: successful execution does not automatically mean successful data quality. Always verify the destination during testing.
Step 9: Schedule Your Scenario
After the scenario works correctly, configure scheduling according to your business requirement.
You might run an automation every 15 minutes, hourly, daily, or according to another suitable schedule. Avoid running a scenario more frequently than necessary because repeated executions can increase operation usage.
For example, urgent lead processing may need frequent runs, while a daily reporting workflow may only need one scheduled execution per day.
Step 10: Turn ON Your Scenario
Once testing and scheduling are complete, turn the scenario ON.
Your automation can now run according to the schedule you configured.
You have completed the core workflow in this Make.com Iterator Tutorial: source data enters the scenario, an array can be split into individual bundles when required, and each item can be processed separately by the destination module.
Iterator vs Array Aggregator in Make.com
Beginners often confuse the Iterator with the Array Aggregator, but they perform opposite jobs.
| Tool | Purpose | Simple Explanation |
|---|---|---|
| Iterator | Splits an array | One array → many bundles |
| Array Aggregator | Combines bundles | Many bundles → one array |
If you need to process each item separately, think Iterator. If you need to combine several processed bundles into one array again, think Array Aggregator. You can read more in Make’s official Aggregator documentation.
When Should You Use a Make.com Iterator?
A Make.com Iterator is useful when a previous module gives you an array and you need the following action to run separately for every item. Common examples include:
- Processing multiple API results
- Handling order line items
- Working with product arrays
- Processing lists of contacts or leads
- Handling multiple attachments
- Creating individual database records
- Processing AI-generated lists
- Working with structured JSON arrays
Common Make.com Iterator Problems and Fixes
1. The Iterator Does Not Show My Array
Run the previous module once using representative sample data and inspect the output. Confirm that the value you want to map is actually an array.
2. My Source Already Produces Multiple Bundles
You may not need an Iterator. Iterator is designed to split an array inside a bundle; it is not automatically required whenever a module returns several results.
3. Airtable Receives the Wrong Information
Review the field mapping and make sure each Iterator value is connected to the correct Airtable field.
4. The Automation Creates Duplicate Records
For production workflows, add a reliable method to identify already processed records. Depending on your workflow, this may involve a unique ID, status column, filter, search-before-create logic, or an update/upsert strategy.
5. The Scenario Works During Testing but Not Automatically
Check that the scenario is ON, scheduling is enabled, app connections are active, and the source data meets your workflow conditions.
Make.com Iterator Best Practices
- Inspect the source output first: confirm that you actually have an array.
- Test with a few items: avoid processing hundreds of records during initial testing.
- Use clear field names: good data structure makes mapping easier.
- Check operation usage: every item can cause downstream modules to execute.
- Prevent duplicates: build a clear processed/unprocessed strategy for recurring workflows.
- Use filters: process only items that meet your business conditions.
- Name modules and scenarios clearly: this makes troubleshooting easier later.
Real-World Make.com Iterator Automation Ideas
| Automation | Example Flow |
|---|---|
| Lead Management | Lead Array → Iterator → CRM |
| Order Processing | Order → Line Items Array → Iterator → Processing |
| Email Attachments | Email → Attachments Array → Iterator → Cloud Storage |
| AI Content Workflow | AI List → Iterator → Process Each Idea → Database |
| API Data Processing | API Response → Results Array → Iterator → Business App |
| E-commerce | Order Data → Product Array → Iterator → Inventory Workflow |
Frequently Asked Questions About Make.com Iterator
What does Iterator do in Make.com?
The Iterator converts an array into separate bundles so subsequent modules can process each array item individually.
When should I use an Iterator in Make.com?
Use an Iterator when a previous module contains an array and you want the following module or modules to process each item separately.
What is an array in Make.com?
An array is a list containing multiple values or collections. An Iterator can separate those array elements for individual processing.
What is a bundle in Make.com?
A bundle is a package of data that moves through modules during scenario execution.
What is the difference between Iterator and Array Aggregator?
An Iterator turns one array into multiple bundles. An Array Aggregator collects multiple bundles and creates an array.
Why can’t I see fields after the Iterator?
Make may not yet know the structure of the data. Run the previous modules once with sample data, then reopen the mapping panel and inspect the available output.
Can I connect a Make.com Iterator to Airtable?
Yes. When an Iterator outputs individual bundles, their fields can be mapped to Airtable or another supported destination module.
Final Thoughts
The Make.com Iterator is one of the most useful tools to understand when you start building more advanced no-code automations. The key concept is simple: when you receive a genuine array and need to process its elements individually, Iterator can split that array into separate bundles.
In this Make.com Iterator Tutorial, you learned how to create a scenario, add modules, configure the source, map an array, connect Airtable, test the workflow, schedule it, and activate the automation.
Once you understand this concept, you can apply it to API responses, order items, attachments, AI-generated data, product lists, lead processing, database workflows, and many other business automations.
Continue Learning Make.com on XVIFS
If you are new to Make.com, continue with the XVIFS Make.com Tutorial for Beginners.
You can also learn how webhooks work in the XVIFS Make.com Webhook Tutorial.
Explore XVIFS for more practical guides covering AI tools, SaaS, workflow automation, productivity, and business technology.
