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.

All of the examples for unsubscribing a REST HOOK, including the code generated from the form based app, show the function returning a value, for instance:
https://github.com/zapier/zapier-platform/blob/master/example-apps/rest-hooks/triggers/recipe.js
 

Unfortunately all of the examples merely show passing through the return from the web request without any particular detail and as far as I can find it is nowhere documented what the upstream code *expects* to be returned here or what the implications of various options are. 

Does the the return value of this function actually do anything?

I don’t think Zapier is doing anything with the body from the unsubscribe response. I think Zapier will, at most, just look for a 200 status to ensure the unsubscribe request didn’t fail. Unsubscribe is called when the Zap is paused… so there wouldn’t be anything in the workflow to pass that data to, and the subscription on Zapier’s side is gone at that point. 

Terms & Conditions