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 use a API call to retrieve items in bulk , if there are more then 1000 entries , it gives me a __next option, I use paths to check if this __next option is returned and if true , I run a different API Call with this info. 

but I need to run this call as many times as the response returns this __next option  , I can do this with paths, but I want to re run the last path as many times as necessary , otherwise I need to code more then 50 paths to be sure. . . . 

is there a way to loop this ? 

so , call api call 1  
if response contains __next 
run api call 2
if response contains __next 
run api call 2 
and so forth 

So I want the path go back  and rerun the last path as many times as necessary 

This is a good question, and one I often come up against. The short answer is - It depends on what you’re trying to do, and what your Input/Output is.

 

I’ll provide a couple of scenarios and ways I’ve dealt with this:

 

  1. First off -  you could run a code step before it gets to your path to sort out all the data and give it the appropriate value. I’ve done this for quite a few bigger workflows with good results

But not everyone can write code, or wants to write code

  1. Another way to think about it could be dealing with the end state, and creating a zap for the path you’re referring to. One that literally takes all your data and then triggers an individual zap on each 

I realise these are both a bit advanced, and I’m quite sure there are many way to accomplish what you’re trying to do, but without knowing the applications, and the data you’re working with, that’s all I can suggest for now

Terms & Conditions