Hi @Nagamanickam!

I want to make sure I’m understanding what is happening. It sounds like you are saying you have pagination working for this trigger when it is used in a dynamic dropdown, but it is not working for the actual trigger. Is that right?

Can you tell me the details of how you are assessing it is not working for the actual trigger? How are you testing it, and what is the reason you think the trigger should go to a second page?

The pagination in triggers will not automatically request a second page of results. You would need to manually code the app to request extra pages.

If the problem you’re trying to solve is for more new items being created during the polling interval, you might find moving to a webhook trigger or supporting transfer for your users, though that is a beta feature currently.

Thanks!

Hi @shalgrim 

Yes, your understanding is correct.

I am testing the trigger through publishing zap.

I have attached my code window screenshot below.

Here, in my API I have eight contacts and I am setting per page result as two so as per this query I will have 4 pages. But zap getting successful for only 2 contacts, it’s not getting the second page.

Below is a Zap history screenshot:

You can see the sidebar task section it’s showing only 2.

I have a question, will the page number change automatically or do we have to change the page using code?

If there is a possibility to change the page number using the code, could you please share a sample code?

Thanks in Advance.

Okay, I understand. 

Zapier triggers will not automatically go fetch extra pages when they are run. The pagination feature is for dynamic dropdowns, not polling triggers. I recommend a much larger page size.

If you need to request multiple pages during a single poll, then you’ll have to put your requests inside a loop that would terminate whenever the API indicated there were no more pages to retrieve.

Hope that helps! Let us know if you have more questions