Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hey everyone!

So, in a custom Zapier integration hook trigger, is it possible to make it show the webhook URL in the UI instead of calling performSubscribe? A similar behavior can be seen in WooCommerce app triggers. I need this because in some APIs (like Dropbox), it isn't possible to subscribe a webhook programmatically which means that the user has to copy/paste the webhook URL manually in their app dashboard.

Any ideas on how to achieve that? Thanks!

Hi there!

I just wanted to clarify something. Are you referring to this in the WooCommerce integration (now only in their legacy integration, since they recently updated it to no longer use this method):

 

 

Is this what you’re looking to do, where a URL is provided and you would then copy it and use it in the app from which you’re sending data? Or were you looking to do something different? Thanks!

Hi @nicksimard - Thanks for your response!

Yep, that’s exactly what I’m referring to. Is that possible? Is there an undocumented configuration that would allow to achieve that?

Cheers!

After experimenting a little bit more, it turned out that performSubscribe is not required for the trigger to work. The solution was so simple, I couldn’t believe that I hadn’t thought of it before. So I just omitted performSubscribe and performUnsubscribe from the trigger definition and it worked!

Terms & Conditions