Add static webhooks for each integration trigger
GibsDev opened this issue · comments
Current Behavior
In order to receive a webhook from an application, the application needs to implement rest hooks, or Zapier will generate a new webhook url per zap when only specifying the perform function within a trigger.
Desired Behavior
Each trigger can be (optionally) set to have a statically assigned webhook url so you do not need to register a new webhook url in the application each time you implement the trigger into a zap.
These static webhooks urls should also be displayed for each trigger when running zapier describe in CLI (after a valid push has been made)
Each trigger can be (optionally) set to have a statically assigned webhook url so you do not need to register a new webhook url in the application each time you implement the trigger into a zap.
I don't quite follow the request here. Can you be more clear about who needs to do what? I'm mixing up who "you" is- he developer or the end user?
For what it's worth, I think you're describing how rest hooks work. When a zap is turned on, the zap sends its unique URL to the external service (thereby "registering" it) and the end-user doesn't need to do any extra steps.
For the static webhook, each zap gets its own webhook url and the end user has to paste that url into the external service (once for each zap). Are you wanting the same static webhook url to be used for multiple zaps (but still unique to that user)?
Are you wanting the same static webhook url to be used for multiple zaps (but still unique to that user)?
Yes, exactly this.
As a third party integration creator, it is not possible to modify the application to implement rest hooks. But in most cases you can manually add a webhook url. Rather than having to manually register webhook urls for each zap (implementation), it would be very useful to only need to register a single webhook url and that information will be passed to all implementations of a certain trigger.
At first I was completely oblivious to keeping webhooks unique to a user, as I am going to be the only one using my integration, but I see now how that is challenging.
Perhaps this could be done in a similar manner to how accounts are stored and available through a dropdown for actions? The zap creator/implementer could select from a list of existing webhooks, or create and add new ones as needed.