Help with Iterator: http dynamique value only return one value instead of 20

[Nael_SID_ALI]

Hi everyone,

I’m trying to automate a workflow in Make.com to retrieve coffee shop listings from Google Places API and store them in a Google Sheet. The HTTP module successfully returns 20 results in the JSON response, but I’m facing two major issues.

1. Iterator only processes one result instead of 20

• The HTTP request to Google Places API correctly returns a JSON array (results) containing 20 coffee shops.
• However, when I use an Iterator to process each business individually, it only outputs one result instead of 20.
• It seems that the entire array is inside a single bundle rather than being split into 20 individual bundles.

How can I properly iterate over each establishment in results?

2. Handling next_page_token to get all coffee shops

• Google Places API paginates results, so I need to fetch additional pages using next_page_token.
• I have set up a router to detect if a next_page_token is present and trigger another HTTP request.
• However, I’m not sure if the second batch of results is being added correctly to my Google Sheet.

How do I ensure that results from multiple pages (via next_page_token) are properly aggregated and stored in Google Sheets?

Current Setup in Make.com

• HTTP Request (GET) → Router → Iterator → Google Sheets (Add Row)
• A second branch handles next_page_token but might not be working as expected.

I have attached screenshots of my scenario for better understanding. Any help or suggestions would be greatly appreciated!

Thanks in advance!

blueprint (1).json (105.6 KB)

[samliew]

Welcome to the Make community!

You are not mapping the array correctly.

It should only contain 3.data

For more information, see https://academy.make.com/courses/IntermediateC01

“Looping” Through Array Items

When you see an ARRAY, think ITERATOR module.

Then,

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:

• Array aggregator
• Text aggregator
• Numeric aggregator
• Table aggregator
• JSON aggregator
• CSV aggregator
• Archive (ZIP) aggregator
• other app-specific aggregators

For more information, see Mapping with Arrays link below.

Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —

Getting Started

• Help Centre | Tutorials – Make “Manual”
• Make Academy – Basics 101: Learn Make and get certified

Help Centre Basics

• Mapping – What is mapping? What can I map?
• Mapping with arrays – How to map items in an array
• Aggregate an array for mapping complex fields
• Date Format: tokens for parseDate | tokens for formatDate
• HTTP modules – Make a request, Get (download) a file
• Webhooks – Error Handling, Responding to webhooks

Articles & Videos

• Router Magic Formula - YouTube
• Error Handlers in Make - YouTube playlist
• Getting started with OpenAI - How to setup and use OpenAI (ChatGPT) in Make
• How to use Regex in Make - How to use pattern matching to extract the text you want
• Webhooks – Make Academy – tutorial on how to use Webhooks

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.