By default, Zapier triggers fetch new or recently updated data to start Zaps, and only need to find the most recently added items. Triggers can also be used to populate dynamic dropdown fields, and there they need to find all possible items to populate the field.
bundle.meta.page
value which tracks the pages Zapier has loaded, along with a Load more option in the user-facing Zapier editor’s dropdown menus.bundle.meta.page
in your API call as Zapier does not include that automatically, then add a new URL Param for your API’s paging option (or optionally add it to your HTTP Headers if your API expects the paging value there). Use the page request field name from your API on the left, and {{bundle.meta.page}}
on the right to have Zapier pull in the correct page value.bundle.meta.page
value uses zero-based numbering. The first time Zapier fetches data from your API, it uses a page value of 0, followed by 1 the second time, and so on. If your API expects the first API call to request page 1, with 2 for the second page and so on, you’ll need to switch to code mode and add + 1
to bundle.meta.page
. So pagination in the code would look like the below (substituting page
with the correct field name your API uses for pagination):
'page': bundle.meta.page + 1
page=0
value (or the correct term for pages in your API) under the Request Params header by default, or page=1
if you’re customizing the page requests to start at 1.