A short guide to what n8n version control is, why Git fits it, and how n8n 2 Git delivers it for self-hosted n8n.
n8n version control means tracking changes to your n8n workflows over time: who changed what, when, and the ability to roll back or compare versions. Self-hosted n8n does not ship with built-in version control; enterprise features aside, the usual approach is to store workflow JSON somewhere and manage history yourself. Using Git (and GitHub) as that store gives you the same versioning model you use for code: commits, branches, and a full history in a standard tool.
Git is the standard for version control. Storing n8n workflow JSON in a Git repository means you get a clear history, the option to use branches for experiments, and the ability to collaborate via pull requests. Your workflows live in your own GitHub repo—private or public—so you keep control of the data and can reuse the same workflows across instances or restore them after a migration.
n8n 2 Git is a Chrome extension that adds push and pull to the n8n editor. You connect your self-hosted n8n instance to your GitHub repository; then you push the current workflow to Git or pull the latest version from Git directly from the n8n UI. It works with n8n 1.x and n8n 2.0. On n8n 2.x you can optionally auto-commit when you publish, with the version name and description used as the commit message. There is no need for n8n Enterprise—you get n8n version control with Git and GitHub for your self-hosted setup.
To get started, install the extension from the Chrome Web Store, register your n8n domain on this site, and follow the configuration guide to connect GitHub. For the full product overview and pricing, see the n8n 2 Git homepage.