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’ve run into the 5-path limit in my Zap and I’m wondering whether it’s possible to get more than that.

The use case: I'd like 16 options for paths so I can get an sub/unsub action for 8 different Mailchimp lists. I really won’t want to set up 16 different Zaps for this. 

Possible?

Hey @ZapsAndApps!

There’s a pretty cool secret to Paths that you might not have seen, yet. Paths can go “five wide and three deep” meaning that you can have 3 Paths nested under your 5 initial Paths and then an additional 3 Paths under each of those. 

Might that work for your use case? 

However, often times the same workflow can be accomplished with the addition of a lookup table. A Lookup Table is a way to match a value and transform it into something else. 

 

You can read more about it here: https://zapier.com/help/create/format/create-lookup-tables-in-zaps

Hope that helps!

Hi @ZapsAndApps 

Good question.

Another approach to creating paths is by chaining Zaps together with Webhooks: https://zapier.com/apps/webhook/help

Example: Zap A action (Webhook) sends data to Zap B trigger (Webhook)

This allows for these configurations

  • 1:1
  • 1:MANY
  • MANY:1

Hey @ZapsAndApps!

I just wanted to check-in here to see if the suggestions provided here helped get you unstuck?

Especially with what you described I do think a lookup table could be a super elegant solution, since it sounds like this time the only difference in the actions each path would take is selecting a different list, the output of the lookup table can be used to make that field dynamic in a single action so your Zap will be much simpler!

I would be more than happy to take another look if you ran into any trouble with that but hopefully you are all set now!

@PaulDavidson yup I’m all set with the answers above :) 

Thanks to you, @Troy Tessalone and @nicksimard for the help. It’s good to know about all the options:

  • nested Paths
  • webhooks for 1:1, 1:MANY and MANY:1
  • lookup tables

One of these will definitely allow us to do what we need!

Terms & Conditions