Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I followed the steps mentioned in the developer documentation. But I am not getting the second-page results.

I checked this trigger with a dropdown which is working as expected.

please help us with this and how can we achieve this.

 

Thanks in advance.

Hi @Nagamanickam - Did you check the Support Paging checkbox?

 

 

Hi @ikbelkirasan Yes I did

Hey @Nagamanickam! 👋

Just to confirm, checking the “Support Paging” checkbox on the trigger means that bundle.meta.page will be incremented by 1 every time the “Load More” button is clicked in the Zap Editor on the dropdown field that uses that trigger, like the example from our help page below:

9a969f577adcb1d9e9c113531f8b99b0.png

Your screenshot shows that the value bundle.meta.page + 1 is being sent in each GET request via a page querystring parameter, so that looks good:

fe277aee2605b9e05b33cbdfcf4f61e2.png
As the first page of results is being successfully returned, is there any chance that there just isn’t a second page of results available in the app?

If there are definitely more results to be returned, please could you complete the following as next steps in troubleshooting:

Test via the Developer Platform

1. Check the documentation for the API you’re using to make sure that the pagination parameter and value are being sent exactly as the API needs.

2. Manually test the trigger via the “Test your API Request” section as per the example here: https://platform.zapier.com/docs/triggers#pagination. Click the “HTTP” tab and then check the details shown in the “Request Params” section. Confirm that the pagination parameter and value are being correctly sent:

a2369c9f4074dd10413ef7bc5ac64096.png

Test via the Zap Editor

Click the “Load More” button on that dropdown field in a Zap, then tracking down the associated GET request via the “Monitoring” section of your app. Check the request details to make sure that the pagination parameter and value are being sent exactly as you would expect.

I hope this helps! If not, please could you post the following:

  1. A link to the documentation page for the API you’re using that shows the details on how pagination works.
  2. Screenshots showing the details from the “Monitoring” page for a GET request sent after the “Load More” button was clicked in the Zap Editor.

Hi @iansco 

Can you please share some sample source code or resources for how polling works with pagination?

Thanks 

Nagamanickam

Hey @Nagamanickam 👋

The documentation for pagination is here: https://platform.zapier.com/docs/triggers#pagination - though I believe you’ve found this already from the screenshots of your code 👍

What you’ve implemented would be expected to return the second page of results, as long as there is a second page of results available, and the pagination parameter and value are being sent exactly as your API needs.

If you’re still having trouble after trying the next recommended steps in the previous reply, please post the requested API docs and screenshots. 

Terms & Conditions