If an integration is in production, and the need to add fields or functionality arises because the feature set of the source or destination apps increase, will releasing a newer version of the integration cause existing zaps to fail? Or, will the current users of the zap just not have the additional functionality until they make edits to their zaps?
Best answer
Will releasing a new version of an integration break existing zaps?
Best answer by GetUWiredBest answer by GetUWired
Hi
As Troy mentioned, Zapier app integrations can have versions. You can control when to migrate users to a new version. If it is a breaking change, it is best to release a new version i.e 2.0 as opposed to 1.1. You can then deprecate the old app which will slowly cause users to switch to the new version.
if it is not a breaking change, you can release a sub version and migrate users from say 1.0 to 1.1
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
+14- Zapier Expert
- 31058 replies
Hi
Zap app integrations can have Versions: https://platform.zapier.com/docs/versions
+12- Zapier Expert
- 1030 replies
- Answer
Hi
As Troy mentioned, Zapier app integrations can have versions. You can control when to migrate users to a new version. If it is a breaking change, it is best to release a new version i.e 2.0 as opposed to 1.1. You can then deprecate the old app which will slowly cause users to switch to the new version.
if it is not a breaking change, you can release a sub version and migrate users from say 1.0 to 1.1
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.