Skip to main content

Can a trigger have 2 subscribed webhooks?

 

Let’s say I have 2 webhooks which kind of represent the same event in Zapier but which are fired under different circumstances in my own app.

so instead of creating now a 3rd hook which would be used by my Zapier integration and which would be fired under both circumstances in my app, I thought it would be probably cleaner to handle this on the Zapier side.

I’m using following way to subscribe to a hook https://platform.zapier.com/cli_tutorials/resthooks , so in theory I should be able to run the request which subscribes the Zapier webhooks , but I’m not really sure if this is the best approach.

 

Is anybody here doing something similar? 

Hey @Daniel_F!

I’m a little unclear on what you mean by “I have 2 webhooks which kind of represent the same event in Zapier but which are fired under different circumstances in my own app.” - to set up a webhook trigger for an App integration, the webhook trigger must follow the rest hooks protocol: https://resthooks.org/

So if your app supports REST Hooks—webhook subscriptions that can be manipulated through a REST API - you can follow the steps here to build a webhook trigger in the Zapier Developer Platform for each event in your app: https://platform.zapier.com/docs/triggers#rest-hook-trigger 

However, if instead you’ve got an editable webhook setup in your app for two different events, that you want to each trigger the same Zap, you might be better off looking at a Webhooks by Zapier trigger in the Zap itself, which would give you one webhook URL to place in your app for any event that should fire the Zap.

Related threads:

 

 

Hope that this helps - if not, perhaps you could provide an example of the events in your app and what you’re expecting on the Zapier end of things, as well as a screenshot or two of the setup you have in Zapier so far (please block out any identifiable information 👍)