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’m developing a Zapier integration against an underlying Graphql API using cursor based pagination.

What is the recommended way to build my triggers;

  1. Using polling, and implement some js code to “support” cursor based pagination - any links on how to do this?
  2. Using REST hooks. I looked at one of the Github repositories, and it seems like it’s not super active - are REST hooks preferred over polling or?

Thanks for helping me out :)

@alexb - If you want your triggers to run instantly then go for webhooks. Otherwise, polling triggers should be fine.

More info on how to use cursors in a trigger can be found here: https://platform.zapier.com/cli_docs/docs#paging

Thanks for the answer - I will stay with polling then. It makes sense that the polling query needs pagination. Regarding the documentation in the link above - I’m a bit confused as to why it mentions dropdowns? As that simply because the way of pagination is the same as for the polling trigger?

@alexb “pagination” is a concept specific to triggers that populate dropdowns.  When the user selects “load more” in the dropdown we call the trigger again, passing the page parameter, so you can make the appropriate request to your API for the next set of data.  Pagination as described is not a concept that is germane to regular, Zap runtime, polling trigger execution.

 

In your polling triggers you can make multiple requests to pull back more than one page of data if you need to, but you’re in control of that - the platform itself isn’t going to make paging requests when the Zap is running.  

 

Let us know of that doesn’t make sense.  There’s a good bit of overloading of context when we discuss triggers - Zap Editor execution vs Zap runtime execution; and trigger execution to populate a dropdown vs trigger execution to support a Zap runtime polling execution.  So it’s natural for it to be a little unclear at first, unfortunately.  

Hi @Zane .

Thanks for your answer - I’m interested in Zap runtime polling execution 😅

I actually asked a more refined question here, where you can maybe help answer one of the things I currently don’t understand how to achieve speaking about runtime polling execution?

Terms & Conditions