Hi @MartinKjeldP
Good question.
As a workaround, try this…
You can chain Zaps together using Webhooks to achieve the concept of Paths. (Paths have limitations as well)
EXAMPLE
Zap 1
- Trigger: ???
- Action: Webhook - POST
- Triggers Zap 2, 3, etc.
Zap 2
- Trigger: Webhook - Catch Hook
- Use the generated webhook URL in Zap 1, Step 2
- Action: Filter
- Action: Looping
- Action: ???
If you have multiple webhooks you want to trigger from the same event in your app, you can combine their URLs into a single URL. For example, if you have three Zaps, the URLs would look like this:
https://hooks.zapier.com/hooks/catch/123456/zbB61
https://hooks.zapier.com/hooks/catch/123456/kzXC4
https://hooks.zapier.com/hooks/catch/123456/2Ajjn
You can take the last part of each URLs and combine them into a single URL like this:
https://zapier.com/hooks/catch/123456/zbB61,kzXC4,2Ajjn
Requests sent to this URL will trigger all three webhook URLs at once.
Hi @Troy Tessalone
Thank you for your response.
However, your proposed workaround is not viable. The whole point of keeping the actions in a single Zap is to easily follow the steps undertaken, to monitor how data is moved, and to minimise the number of steps and automated tasks.
But thank you nonetheless.
@MartinKjeldP
I think you may want to reconsider this approach, considering it’s a viable solution and you’ve encountered limitations with your current approach to configuring the Zaps.
Paths have limitations.
Max top level Paths: 5
Paths can’t be cloned.
Whereas, Zaps can be cloned and easily edited, while being chained together with Webhooks.
Keep in mind Zap trigger steps do NOT count as Tasks.
Really comes down to properly labeling the Zaps to trace the data flow in the Zap Runs: https://zapier.com/app/history/
@Troy Tessalone
Thank you for the message; however, it would be much more simple if it were possible to use more than one Looping component in a Zap. I am not particularly interested in a workaround that requires me to break a Zap into n-number of other Zaps, as all other objectives of the task are achieved using a single Zap with paths.
So my question remains: Is it correct that only one looping component can be active in a Zap? There seems to be no information available on the limitations of looping components (https://zapier.com/help/create/other-functions/loop-your-zap-actions)
@MartinKjeldP
Can I create nested loops?
Nested loops are not supported. You won’t be able to turn on a Zap with more than 1 Looping by Zapier Step.
Hi there, @MartinKjeldP! Thanks for stopping by.
I wanted to confirm that Troy is indeed correct, regarding Nested loops not being supported at this time.
That said, it is an open feature request! I went ahead and added your vote to this. While I can’t offer any estimates on when or if this will be offered, we’ll be sure to you an email if that changes. We’ll also keep this topic updated as well.
Thanks again for sharing your feedback!