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 have a trigger I am working on that is fired via a webhook. I am stuck on an issue with the trigger data that is retrieved via the perfromList call. In my code I am calling our APIs to retrieve 3 members which works fine on the initial call. The problem occurs when I want to load additional records. When working on this I assumed it would pass to me a incremented page value in the bundle.meta.page but no matter what it always returns 0. So it seems the page does not increment for the test trigger calls for hooks.

 

So essentially I am asking if there is a way to do this or am I going at this in the wrong way? The end goal is to provide users with current live data in these trigger tests so they can properly use setup their zaps.

 

Thank you for any help.

In a RestHook type trigger the performList is only called during Zap setup to retrieve objects representative of what the hook will be sending to the Zap once the Zap is configured and turned on, so that the user can have fields to map into steps of subsequent actions in their Zap.

My first inclination is just to return a bigger set of objects from the single request to performList - if there’s a reason why a user may need a bigger selection of options in object to use for mapping. 

You make a good point that we have a “load more samples” button that feels like something where pagination support could come into play. I’ll raise that with the editor team for future consideration. Today pagination is only relevant to triggers that power dynamic dropdowns, but it will also power a cool new offering Zapier is bringing out soon.

 

Terms & Conditions