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 would like to request a feature! Here is what it is. 

 

Many times when using “Paths” as a function, the various paths are all very similar with a couple of minor changes. 

What I would like - is the ability to take one branch of a path, and copy/paste it to be the second or third option of the path instead of having to go re-make every step in the path over again. This would save a ton of time!

 

Thanks!

Hi @AppGuyAaron 

Feature requests can be submitted to Zapier Support: https://zapier.com/app/get-help

@AppGuyAaron 

NOTE: Paths have current limitations of 5 top level paths.

 

Advanced workarounds include using Sub-Zaps or using Webhooks to chain Zaps together.

Sub-Zaps: https://zapier.com/apps/sub-zap-by-zapier/integrations

Webhooks: https://zapier.com/apps/webhook/integrations

@Troy Tessalone thanks. Understood on the limitation of paths, but it still means were potentially duplicating a path five times. 

 

Ill have to look into that Sub Zap, I dont know that one.

@AppGuyAaron

I’d suggest designing your Zaps differently by decoupling Zaps that would use the Paths app for the reasons you’ve mentioned.

Instead, you can achieve the concept of paths using Sub-Zaps or Webhooks to chain Zaps together.

 

Webhooks can be used as an action (e.g. POST) to then trigger another Zap (e.g. Catch Hook).

This allows you to design Zaps in a more modular way and makes it easy to copy/edit a Zap and include as a chained Zap.

TIP: Multiple Zaps can be triggered from 1 webhook: https://zapier.com/help/create/code-webhooks/trigger-zaps-from-webhooks#optional-trigger-multiple-zaps-with-webhooks

 

Sub-Zaps are meant for reusing Zaps as a sub-routine across other Zaps.

Data you specify is sent in and data you specify is returned, then the main Zap can continue.
Think of this as repurposing common components.

Terms & Conditions