Marketing automation
Announcing Autosave & More!
We’re introducing a safer and more reliable way to manage your workflow development lifecycle with the arrival of Autosave, Versioned Publishing, and Concurrency Protection.
For a long time, Autosave has been the most requested feature from the community. But implementing it wasn’t as simple as just removing the “Save” button. In previous versions of n8n, “Saving” an active workflow was synonymous with “Deploying” it. If we had simply enabled Autosave in that environment, every half-finished node configuration or temporary break in logic would have been pushed live to production instantly.
To give you Autosave, we first had to fundamentally change how n8n handles workflow states. We had to decouple the act of saving your work from the act of deploying it live.
This post explains how Autosave and Publishing work together to provide a safety net for mission-critical automations.
TL;DR
• Autosave launched in Beta with version 2.4.0
• Available for everyone – free self hosted, cloud, and Enterprise.
• No migration or actions required to start using.
• The save button is no more.
How It Works:
Let’s look at the key mechanics that power the new workflow lifecycle.
Autosave
This is the headline change. You no longer have a save button. The editor now checks for changes every two seconds and saves them automatically. No need to worry about browser crashes, accidental tab closures, or plain simple “I forgot to save this” situations.
Versioned Publishing
In the past, Saving an activated workflow meant instant changes to live. Now, you have explicit control over which version of your workflow is live. You can continue to make changes and iterate on your workflow for days while the Published version continues to run the old, stable logic.
Note: Publishing was added in v2.0.0
Version History (your new control center)
The History panel is now a mini “Command Center” for your workflow. Track changes, perform instant rollbacks, or publish any previous version.
Concurrency Protection
n8n now detects when a colleague is editing a workflow and temporarily locks the canvas in Read-Only mode for everyone else, ensuring you never accidentally overwrite each other’s active work.
The Workflow Lifecycle in Action
The best way to understand this new lifecycle is to see it in practice.
Let’s walk through the following scenario:
- Creating a new workflow
- Publishing it (making it live)
- Safe updates (updating an already published workflow)
- Publishing a new version
- Rolling back to a previous version