Descriptions:
Bart Slodyczka walks through the new version control system introduced in n8n 2.0, explaining how it changes the way automation builders manage, test, and roll back their workflows. The update establishes a meaningful distinction between two buttons that previously caused confusion: the Save button, which captures a snapshot of the current workflow state without affecting what’s live, and the Publish button, which actually activates the workflow and generates the production webhook URL.
With n8n 2.0’s version history panel, users can view all saved snapshots alongside the currently published version, instantly switch between them, and roll back to a previous working state when a new change breaks something. Bart demonstrates this by building a simple AI agent automation — starting with a chat node and incrementally adding a code node and an HTTP tool call — saving snapshots at each stage to show how version history accumulates in practice.
The video also covers strategies for working around the free tier’s one-day history limit: cloning a specific snapshot into a new workflow for isolated testing, copying workflow JSON to overlay onto an existing canvas, and using version snapshots as a logging foundation when building automations expected to handle hundreds or thousands of weekly runs. For teams running production automations in n8n, the version control feature significantly reduces the risk of breaking live workflows during active iteration and provides a safety net that was previously absent from the platform.
📺 Source: Bart Slodyczka · Published December 10, 2025
🏷️ Format: Tutorial Demo
