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.
@Nagamanickam - Did you check the Support Paging checkbox?
@ikbelkirasan Yes I did
Just to confirm, checking the “Support Paging” checkbox on the trigger means that
bundle.meta.pagewill 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:
Your screenshot shows that the value
bundle.meta.page + 1is being sent in each GET request via a
pagequerystring parameter, so that looks good:
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:
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:
Can you please share some sample source code or resources for how polling works with pagination?
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.