Deprecate or delete a version
Deprecation is an optional process that allows you to set a date from which a non-public version of your integration will no longer be updated. Deprecation is only recommended if the older integration version will eventually stop working, such as if the related API will be removed. Zapier is normally a “set it and forget it” experience for users, so use this feature carefully. Only if the older version will no longer function, should it be deprecated. Please note that deprecating a version is significantly more disruptive to our mutual users than migrating to the latest promoted version, or than leaving users on an older (now) private version if migration is not possible.
When users are left on an older private version, they will see a prompt in the Zap editor to optionally encourage them to make the update, instead of any deprecation communications or Zap disruptions.
What happens after setting a version to deprecate
1. Email notification
After setting the deprecation date, if the date is in 30 days or less, an initial email will be immediately sent to users, informing them that they need to manually update their Zaps to continue using the new version. If the deprecation date is more than 30 days into the future, then the notification email will be sent exactly 30 days before the configured deprecation date. Zapier recommends supplementing these automated messages by also notifying your general user base through in-app announcements or email marketing campaigns. For privacy reasons, Zapier cannot provide you with an email list of users of your integration.
2. Deprecation date reached
- Zaps that haven’t been updated will be automatically paused.
- Any attempts to run triggers or actions on the deprecated version will result in an error.
- A second email, titled “X Zaps paused over deprecated apps,” will be sent out to those users. Customizing this email is not possible.
- The deprecated version will be labelled as “Deprecated” in the Zap editor, with a prompt for users to update to the latest version.
3. Post-deprecation
After the deprecation date, the version will still be visible in the Versions page for your future reference. Users will not be able to see the version once they select a different version in their Zaps.
Deprecate a version with Platform UI
To deprecate an integration version:
- Log into the Platform UI.
- Select your integration.
- In the Manage section in the left sidebar, click Version.
- Click the three dot icon in line with the integration version you want to deprecate.
- Click Deprecate.
- In the dialog box, add the Deprecate Date. You can set a deprecation date anytime between 2 weeks and 1 year from the current date.
- Click Deprecate.
- Click Close
Deprecate a version with Platform CLI
To deprecate an integration version use the command zapier deprecate. Learn more about Platform CLI commands.
Deleting deprecated versions
After your version has been deprecated, you have the option to delete versions entirely. Exercise this option with extreme caution. Deleting a version makes it permanently inaccessible, both to you and to your users. Deleted versions cannot be restored by Zapier Developer Support.
In most scenarios, it’s advisable either to deprecate the version or leave it as a private version. Deletion should be a last resort, used only when you are certain that the version will never be needed again.
Deletion is also only possible when 0 users remain on a version. The count of users on the Versions page includes live Zaps only. If you’re seeing the error Unable to delete app version, this can be caused by users on that version not included in the visible count (paused Zaps, app authentications for example).
Need help? Tell us about your problem and we’ll connect you with the right resource or contact support.
Was this page helpful?