Workflow Versioning
Workflow Version Control System (W-VCS)
Section titled “Workflow Version Control System (W-VCS)”Kizuna introduces an enterprise-grade version control system tailored specifically for n8n workflows. While n8n provides local execution history, Kizuna offers true immutable snapshots of your workflow logic.
Why use W-VCS?
Section titled “Why use W-VCS?”- Disaster Recovery: If you accidentally delete a node or break logic, restore a working version instantly.
- Migration Safety: Save a snapshot before migrating a workflow to a new server.
- Audit Trails: Keep a named history of changes (e.g., “v1.0 - Initial Release”, “v1.1 - Added Error Handling”).
How it Works
Section titled “How it Works”1. Saving a Version
Section titled “1. Saving a Version”In the Workflow Details view, click the “Save Version” button. You can provide a custom name and description for the snapshot.
- The entire JSON of the workflow is encrypted and stored in Kizuna’s database.
- Metadata (creator, timestamp, tags) is attached.
2. Browsing History
Section titled “2. Browsing History”The “Versions” tab displays a timeline of all saved snapshots.
- View Code: Inspect the JSON of any version directly in the browser.
- Download: Export specific versions as
.jsonfiles for local backup.
3. One-Click Restore
Section titled “3. One-Click Restore”The Restore feature allows you to overwrite the live workflow on your n8n server with any saved version.
GitHub Integration
Section titled “GitHub Integration”For teams that prefer Git-based flows, Kizuna supports direct Push to GitHub.
- Configure your GitHub Token in
Settings. - Select a repository and branch.
- Push workflow changes with a commit message directly from the Kizuna UI.