Use source control and environments

Feature availability

• Available on Business and Enterprise plans.

• You must be an n8n instance owner or instance admin to enable and configure source control.

• Instance owners and instance admins can push changes to and pull changes from the connected repository.

• Project admins can push changes to the connected repository. They can't pull changes from the repository.

n8n uses Git-based source control to support environments. Linking your n8n instances to a Git repository lets you create multiple n8n environments, backed by Git branches.

In this section

• Understand source control: how source control and environments work in n8n.

• Work with environments: the purpose of environments, and how they work in n8n.

• Use Git in n8n: how n8n uses Git.

• Choose branching patterns: the possible relationships between n8n instances and Git branches.

• Set up source control: how to connect your n8n instance to Git.

• Push and pull changes: send work to Git, and fetch work from Git to your instance.

• Compare versions: use workflow diffs to compare local and remote changes.

• Move work between environments: how to copy work between different n8n instances.

• Use environments programmatically with the public API: preview, push, and pull source control changes using the n8n public API.

• Tutorial: Create environments with source control: an end-to-end tutorial, setting up environments using n8n's recommended configurations.

Related sections

• Variables: reusable values.

• External secrets: manage credentials with an external secrets vault.

Related resources

• Administer

• Manage users and access

• Manage credentials

• Observe and log