HTTP: Integrated Paging of API results
complete
Alex Sirota
In some situations an API will return results in a paging format. Since the results may return thousands of objects the API has a feature to return a certain number of results per page and a way to return the next page until there are no results.
Currently to integrate this requires a use of an iterator with a fancy page counter to keep track and aggregate results in one large object.
Having a module be able to specify max results or just be able to internally perform the paging without any extra operations would be ideal.
Log In
Tereza Klobouckova
marked this post as
complete
Dear Makers,
we’re thrilled to announce that the new HTTP (v4) app now features native, built-in pagination!
You can now fully leverage LIST and SEARCH endpoints without manually orchestrating page-by-page retrieval at the scenario level. The module handles iteration logic internally, replacing complex workarounds with a simple configuration that saves you time and costs.
Make’s HTTP app now supports all commonly used pagination patterns, including:
🔹 Cursor / Token
🔹 Offset
🔹 Page number
🔹 URL
All you need to do is configure the module to understand which request parameters it should send and which response fields it should parse. Once set up, the module automatically retrieves the pages and returns a unified, clean output, so you can focus on what matters: your data. ✨
Give it a try and experience simpler, faster, and more efficient pagination in your automations.
Resources:
📚 Get started with our technical guide: https://www.make.com/en/help/app/http
📝 Read the full release notes: https://help.make.com/new-http-app-is-now-available
Happy Automating!
Tereza
The Make Team
Tereza Klobouckova
marked this post as
complete
Dear Makers,
we’re thrilled to announce that the new HTTP (v4) app now features native, built-in pagination!
You can now fully leverage LIST and SEARCH endpoints without manually orchestrating page-by-page retrieval at the scenario level. The module handles iteration logic internally, replacing complex workarounds with a simple configuration that saves you time and costs.
Make’s HTTP app now supports all commonly used pagination patterns, including:
🔹 Cursor / Token
🔹 Offset
🔹 Page number
🔹 URL
All you need to do is configure the module to understand which request parameters it should send and which response fields it should parse. Once set up, the module automatically retrieves the pages and returns a unified, clean output, so you can focus on what matters: your data. ✨
Give it a try and experience simpler, faster, and more efficient pagination in your automations.
Resources:
📚 Get started with our technical guide: https://www.make.com/en/help/app/http
📝 Read the full release notes: https://help.make.com/new-http-app-is-now-available
Happy Automating!
Tereza
The Make Team
Tereza Klobouckova
Merged in a post:
Allow for multiple HTTP get requests
Brendan Reynolds
Allow for multiple HTTP get requests to happen concurrently when arrays are inputed into the request parameters.
Tereza Klobouckova
Merged in a post:
HTTP: Pagination Support
Michal
The pagination is not rocket science but design it piece by piece over and over is like assembling the same puzzle all the time. It’s time-consuming, tedious and useless Especially in automation tools like Integromat, Zapier or MS Automate it is not a pleasant task although it is reproducible operation.
There are 3-4 parameters in request in URL or the body and 3-4 parameters in the response body. This simple setup can cover 90 % of APPs’ pagination procedure. Custom repeaters must solve the rest (non-standard paginations).
Please, add pagination support to the HTTP request and make the life more comfortable.
ProLingua
I created a post about this issue and some others about scenario interoperability: https://community.make.com/t/summary-of-improvements-for-scenarios-interoperability/62659
ProLingua
I created a post about this issue and some others about scenario interoperability: https://community.make.com/t/summary-of-improvements-for-scenarios-interoperability/62659
Craig Steddy
and we're still waiting... :-(
Bruno Thomé
It should be possible to do this with recursion instead of the iterator.
The only way I could think of doing this with an iterator/repeater was actually setting up a loop with more runs than pages, then checking every run if a flag variable was set. Pretty crappy and operation-intensive.
Here, this is a bit different, but can illustrate the idea. If I try to Watch Changes recursively in GDrive, I can do something like in the image.
Tom Solid
Alex Sirota Yes! Handling "Paging of API results" in Integromat is a pain. Any update on this?
James Word
Yes, please! I hit this problem today. Is there any documentation or do you have any examples on how to use the "iterator + fancy page counter" method?
Thorsten Junus Gorny
James Word:Hi James, I also hit this problem - have you found a solution?
F4mily Matters
Any update on this?
Load More
→