Autosave is finally here.
[UPDATE Jan 13, 2026]
Autosave beta is live - read all about it here:
—–
TL;DR - Autosave is coming next week.
Autosave has been one of the most requested features in n8n history. It’s been on our roadmap for a long, long time. As we sat down to build it, we realized that Autosave is part of a much bigger challenge that we needed to address:
Providing a complete Workflow Development Lifecycle in n8n.
To do that, we needed to ensure that building a workflow follows the same safe principles as writing code: safe edits, versioned deployments, and collision-free collaboration. If we had simply added Autosave in the version 1.x architecture, every change would have been pushed to production instantly. Not a great idea.
Step one was adding the ability to publish a workflow with the v2.0 launch, decoupling the published (live) version from the latest saved version. By separating the “Saved” state from the “Published” state, we created a safe environment for editing and iterating on workflows without affecting the published version.
This new paradigm provides Versioned Publishing and easy rollbacks, capabilities often considered table-stakes for deploying mission-critical workflows.
With that in place, we can now finally add Autosave to n8n.
→ It’s coming out in Beta next week with version 2.4.0. ←
Here’s how it works:
1. The “Save” button is going away
Starting with version 2.4.0, the UI does not have a Save button anymore (R.I.P. Save button), and pressing control-s doesn’t do anything.
2. Autosave is always on
While editing a workflow, n8n checks for changes every 2 seconds. If a change is detected, it will automatically save it. Because we previously decoupled saving from publishing, this is now completely safe. Your auto-saved versions will not go live until you explicitly hit “Publish.”
3. Concurrency Protection (better collaboration)
If you open a workflow that a teammate is currently editing, n8n will alert you and place the workflow in Read-Only Mode. Your canvas will now update as they make changes.
This ensures you never accidentally overwrite a colleague’s active logic. Once they are inactive, the lock releases, and you can pick up exactly where they left off.
4. The “Publish” Button & Instant Rollbacks (launched with version 2.0.0)
If you haven’t upgraded to v2.x yet, this is the most important workflow change to note. Since Autosave does not impact the live version, you must now explicitly click the Publish button to make your changes live.
You can also select a previously published version from your history and click “Publish.” This effectively gives you one-click rollbacks, allowing you to revert production to a safe state instantly while debugging the latest version in the editor.
We wanted to share this context with our community members early so you aren’t surprised when the Save button disappears on the next Beta release. We’re excited to finally bring you a workflow lifecycle that is safe, collaborative, and auto-saved.
A Note on Beta
Changing the fundamental save logic is a complex shift, so as with all Beta features, please avoid using this on mission-critical production instances until the Stable version is released.
Questions?
Please leave them in this thread.
