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.

Hi there, I’m trying to understand Zapier’s rule that: paths must be the last step in a Zap. 

 

My problem is that I need to create logic that applies to all of the 4 paths, but this means I need to create and maintain duplicate logic under each of the paths, where it could just be triggered and executed by all the paths. 

 

My solution would be that I can add further logic to my main Zap after I’ve created conditional branching/paths, so once my paths have been completed, if they meet the conditions, they can redirect and return back to the Home path to execute the next bit of global logic. 

 

I understand this would also require some function to jump back to the Home path, which currently doesn’t exist in Zapier?

 

 

 

Is there a workaround for this problem? Or am I forced to create duplicate logic in each of the paths? 

 

Thank you :) 

...

Is there a workaround for this problem? Or am I forced to create duplicate logic in each of the paths? 

 

Thank you :) 

 

@alske123456789; this is indeed a limitation of Zapier but fortunately there is a quite easy workaround!

You would need to split the workflow into two different Zaps - one that ends with the path and one that starts with the “joined actions”.

To achieve this, you can use this guide:
https://zapier.com/help/create/code-webhooks/trigger-zaps-from-webhooks

As the last path of each path, you can create a webhook that calls your continuation-Zap.

Hi @alske123456789 

Check out these handy Zap apps that may be applicable to your use cases…

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

Looping: https://zapier.com/apps/looping/integrations#triggers-and-actions

NOTE: Both of these apps are BETA apps and could be subject to future changes/updates.

As @MarijnVerdult mentioned, Webhooks work great to daisy-chain Zaps together.

Hi @alske123456789,

Another option would be to include a post web-hook by Zapier step from inside each path. This web-hook would then trigger a new automation that would carry out the steps that you don’t want to rebuild/duplicate in each path.

This would allow you to only build those additional steps once with a web-hook trigger without including each additional step in each additional path. Hope this sheds more light to what @MarijnVerdult and @Troy Tessalone mentioned!

@alske123456789 

Just checking in to see if one of these solutions got you to where you needed to be?

Terms & Conditions