What is your goal?
get different book on google books by using google book API and add it in a google sheet< add a new row>
What is the problem & what have you tried?
When I run my Make scenario, the API keeps returning only the first page multiple times, depending on the configuration of my Repeater module. As a result, the volumes from that first page are repeated multiple times in my Google Sheet.
I also tested the request URL in Postman by setting the maxResults parameter to 20 instead of the default value of 10. However, the response still contains only one page with 10 volumes.
What could be causing this issue? I’d really appreciate your help. Thank you!
Error messages or input/output bundles
when i changed maxResults to 20, i haw this error message "Couldn’t connect
Error: 503 Service Unavailable
Code: ConnectionError
Origin: HTTP (legacy)
Create public scenario page
Screenshots (scenario flow, module settings, errors)
Two separate things are happening here, and the good news is both are fixable in a few minutes.
First, the repeating page: the Repeater module doesn’t paginate anything — it’s just a counter. It runs the modules after it N times, but nothing about your HTTP request changes between runs unless you map the counter into the request. So you’re sending the identical request N times and getting the identical first page back N times. The fix: set the Repeater’s initial value to 0 and its step to 40, then in the HTTP module’s query string map startIndex to the Repeater’s i and set maxResults=40. Now each iteration requests the next page. (40 is the ceiling for maxResults on this API — that’s also why your Postman test at higher values behaved strangely.)
Second, the 503: that’s Google being transiently unavailable, not something you configured wrong. Rather than babysitting it, right-click the HTTP module, add an error handler, and use the Break directive with 2–3 attempts a few minutes apart (you’ll need “Allow storing incomplete executions” on in scenario settings for Break to do its retry job). The scenario then heals itself instead of dying on a blip.
One more thing worth doing while you’re in there: you’re on the HTTP legacy module — the current HTTP app behaves the same for this but is where fixes land going forward.
