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.

Hello,

I am creating an integration for my company to offer our functionality natively on Zapier. 

When configuring a webhook trigger I am given the option to configure an Unsubscribe API which I assume is for when a user stops using the trigger. This is great and can help us keep our webhooks clean.

Our Webhook deletion API requires the ID of the webhook to be deleted/removed/unsubscribed from. How do I make reference to the ID of the webhook that is returned from the ‘Subscribe’ request in the ‘Ubsubscribe’ request?

I see I have access to a `{{bundle.subscribeData}}` batch of variables, but I don’t see any explanation of them or their contents anywhere. I’m also curious about their state between requests. 

Hey @swoogrb 👋🏼

 

You’re on the right track here - {{bundle.subscribeData}} contains the response from the subscribe call. For example, if upon subscription you get back:

{
  "webhook" : {
      "id" : 12345,
      "url" : "someURL",
      "name" : "Test Webhook",
      "events" : "events"
      }
}

^^ This is now the structure of {{bundle.subscribeData}}.

Hope that helps :)

Ah that is perfect, thanks @Bryan S. 

Reply


Terms & Conditions