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-

 

Suppose we have a zapier version 1.20.15, we just clone it and make it a patch version 1.20.16.

Its clone successfully.On this new version (1.20.16) , we removed few triggers and actions.
After that when trying to migrate user to this new version, its say removed action and triggers keys are missing.

Can you please guide how to migrate user to new version after removing (not hiding) few zaps and actions ?

P.S. I also tried by shifting to major version (2.0.0), but still same error).

 

Also attaching screenshot for the error.
 

That’s a breaking change. If any of a users’ Zaps use the triggers/actions that you removed, they would just stop working unexpectedly if that migrate had succeeded. 

Other examples of breaking changes are changing auth, or adding a new required field.

To manage a breaking change, there are three options:

  1. Don’t make a breaking change. :smiley:  If you hide a trigger or action, running Zaps will keep right on working, but anyone making a new Zap won’t see the option. 
  2. Leave users on the old version. Promote the new version. New users/zaps will be configured with the new version of your integration, the old version will be hidden to new users, and the two versions can live side by side as long as your API keeps supporting both.
  3. When you really, really, really need users to stop using the old version, you have to deprecate it. Use this feature sparingly - it’s hard on users. Deprecation will generate an email to users letting them know that something in your integration requires them to come back the Zap Editor to reconfigure Zaps that use your product. You’ll specify a date and on that date all Zaps that haven’t been updated will be paused. It’s a big ask for users, but sometimes API endpoints themselves need to deprecated or teams change their auth method. Deprecation should be reserved as the last option.
Terms & Conditions