There are multiple threads here asking about multiple triggers and the answers, IMHO, have not been able to tackle the main issue in all of them.
I do understand implementing multiple triggers natively on Zapier would require a massive effort, and understand if it is not in the dev team priorities list at this time. What I (and I believe others) would like to know is what is the recommended work around for this limitation.
Conceptually, it would make sense for a Zap to be triggered from multiple sources and it would be very practical in multi-step Zaps, since the user wouldn't need to re-implement all action steps on multiple zaps. Replicated code is always bad, as I know you know. For instance, if the user needs to update something on the workflow, it can be very troublesome and error-prone to have to replicate the change across multiple Zaps.
Duplicating the Zaps and changing the trigger app helps, but not much, as you still have to go through all action steps correcting the reference to the values from step 1.
In my use case, we have a multi-step and multi-path zap triggering from a Alchemer form. We are implementing new functionalities in this workflow that will require it to be triggered by another Alchemer form, as well as from Trello.
What is the best way to achieve this behavior without having to duplicate all action steps.So far, the workaround I have come up with would be to create multiple “trigger zaps” that simple add data to a centralized location and have the single “action zap” trigger as data is added to such location.
Would this be a recommended implementation? If so, what would be a reliable and safe app to use as such centralized hub?
Google spreadsheet rows? Entries in storage by Zapier? Trello cards?
It would be great to have someone from Zapier to help go through the pros and cons of each.
As I write this, an idea came to mind. It would be great if Zapier provided a native app to implement this easily (this could even be an intermediary step towards an actual multi-trigger solution), even if it is just an envelope over Storage by Zapier. Call it “Shared Trigger by Zapier”.
Here's how it'd work:
1- User would create a zap with a trigger step from any app he wants and an action step from the Shared Trigger, where he would populate key-value pairs with data from the first step.
2- One could have as many of such zaps as needed, all centralizing data on a Shared Trigger, identifiable by a master key (pretty much like Diggest)
3- User could then implement a single zap triggering when “New Data” is added to the Shared Trigger
Hope this is somehow useful
Thanks in advance
Best answer by nicksimardView original