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 am working on a workflow to get data about a ticket from one of our internal systems. That ticket may have one or more relations(links) to other entities attached to it. 

I start by GETting the data via API, however Zapier insists on parsing it for me instead of providing raw JSON. Since the number of links can vary, I need to be able to iterate through n number of entries to find a match. 


I kinda reconstructed the relevant data using Formatter so now I have an example with two entries
 

I want to loop through these items and search the “url” key for a match from my input data and if a match is found, extract the “id” value, which I will need to make a separate API call later. I can’t for the life of me figure out a way to do this that yields the ID I need for the next step. 

 

I’m afraid it’s heading down to custom code and that’s pretty far beyond my skillset right now. Anyone out there spot an approach I might be missing?

Thanks!

Hi @Dan R 

Good question.

Have you tried using the Looping app to handle 1+ line items?

https://zapier.com/apps/looping/help

Hey @Troy Tessalone 

Thanks for engaging so quickly! Yes, I am using a loop with a filter step immediately after to test for a match on the “url” attribute.  I figure that’s the most logical way to handle a variable number of items that I will need to sort through.

Here’s what my setup looks like.

The loop (takes Line Items from formatter step)


The Filter (checks that there’s an ID and that the ticket matches)
 

Trying to  continue to the next step where I take the ID and use it as a resource ID for my next API call (no ID available)
  



Is there something I’m missing or any way you can think of to get that ID that passed the filter as an actionable item for a later flow?
 

Thanks!

@Dan R

Every Loop iteration will output the same defined parameters. (e.g. id, url)

So if you are trying to use the ID from the Looping step, you can simply map the “id” parameter from step 7.

When testing the Looping step, only the 1st iteration output will be available to map.

So you’d have to turn the Zap ON to test all the iterations.

Then check your Zap Runs: https://zapier.com/app/history/

Thanks Troy - So to be sure I understand, when I make step 9 after my filter step, just map the ID value from Step 7 (even if the first value shown is incorrect?) because that’s just how Loops work? 

I’ll give it a try this evening, appreciate the help!

@Dan R 

Yes.

For example, if you map the ID from Step 7 (Looping), then on the 1st iteration it will have a value of 8984887, and on the 2nd iteration it will have a value of 8984765.

 

Terms & Conditions