Paths must be the last step in a Zap

  • 1 April 2021
  • 4 replies

Userlevel 1

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 :) 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Userlevel 4
Badge +3


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:

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

Userlevel 7
Badge +14

Hi @alske123456789 

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



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.

Badge +4

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!

Userlevel 7
Badge +10


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