News

Introducing: Version Rollback

Categories: Product Updates Announcements
Introducing: Version Rollback

TL;DR: It’s happening! You now have the ability to rollback your Zap to previous editing versions 🎊

You asked. ✍️ We delivered. 🤝

What’s New At Zapier

This week we rolled out a new feature that will allow users to restore steps from any past versions of their Zaps. The Version Rollback feature is the third milestone in our versioning for Zaps, joining the previously released Version History and Version Preview features.

This new feature gives our automation heroes greater control and security when changing your workflows. With versioning, users can keep track of changes made to their Zaps and revert to a previous version if necessary.

We're confident that Version Rollback will help you feel more confident and secure when editing your mission-critical workflows! 🙌🏽​​​​​​

Here’s what that looks like for you:

The Version Rollback feature works by adding a new option on every version to Edit from this version. This creates a new draft based on the previous version, allowing users to easily make changes while preserving the original version. When an older version is previewed, the “Edit Zap” button updates to “Edit from v#.”

As a bonus, we even snuck in an easy way to delete drafts  😉

Here’s a breakdown of plan types and Version rollback availability: 

 

On a Starter plan and looking to up your Zap game? Take a look at our pricing plans and choose what works best for you!  

This is great!

It would be great if we can do the same for Zaps when in Draft mode, at least an ‘Undo’ button (Ctrl+Z)

e.g.: You haven’t Published your Zap because you are still building it, mapping fields, etc. and by mistake you erased many fields you mapped in ‘X’ field.


Hey @JoseMendioroz

That would be a great idea. I can’t tell you how many times Ctrl + Z has saved me. 😅 I’ve gone ahead and passed along your feedback to our developers as a potential feature request they can tackle in the future. 

In the meantime, if you have any other great ideas or need help with something, you know where to find us! 


We’ve found that the version history/rollback feature has one major drawback….it’s based on the last versions created date.  So if we have a version that was created 7 months ago and someone makes a change that broke it or had unintended consequences then the version history doesn’t even include our last version to go back to.  We had a user who thought they had created a copy of one of our zaps but actually was editing the original.  They made huge changes to it before realizing their mistake but because the original was over the time period we didn’t even have that one prior version.  It would be more useful if the version history could have the last X number of versions instead of versions from a certain time period.  If you want a tiered system then have Pro have last 2 versions, Team have last 5 and Enterprise or whatever have last 10 or something like that.  That was a very rough and disappointing day when we found out what happened and were so excited thinking we could go back to the last version but there wasn’t even one prior version because of the created date limit.


We’ve found that the version history/rollback feature has one major drawback….it’s based on the last versions created date.  So if we have a version that was created 7 months ago and someone makes a change that broke it or had unintended consequences then the version history doesn’t even include our last version to go back to.  We had a user who thought they had created a copy of one of our zaps but actually was editing the original.  They made huge changes to it before realizing their mistake but because the original was over the time period we didn’t even have that one prior version.  It would be more useful if the version history could have the last X number of versions instead of versions from a certain time period.  If you want a tiered system then have Pro have last 2 versions, Team have last 5 and Enterprise or whatever have last 10 or something like that.  That was a very rough and disappointing day when we found out what happened and were so excited thinking we could go back to the last version but there wasn’t even one prior version because of the created date limit.

Exactly! 

An easy Ctrl+Z shouldn’t be difficult to implement either