GitHub Version Control Dashboard for Automation Assets - n8n Workflow

Implement robust version control for your n8n workflows using GitHub. This n8n workflow template provides a dashboard, status syncing, and one-click rollback capabilities.

Workflow Preview

Ready to automate?

Download this n8n workflow template and start using it instantly.

Who is this best for?


  • Automation Developers seeking reliable version control for their complex n8n workflow designs.

  • DevOps Engineers responsible for maintaining stability and tracking changes across multiple n8n instances.

  • Teams requiring audit trails and rollback capabilities for critical n8n templates.

  • System Administrators managing a self-hosted n8n environment.

Overview

Managing numerous automation processes can be challenging without proper version control. This advanced n8n workflow template solves this by treating every n8n workflow as a code artifact stored securely in GitHub. It provides a real-time dashboard showing the sync status (Synched, n8nOnly, GithubOnly) between your running n8n instance and the repository. Furthermore, it incorporates powerful rollback actions, allowing users to instantly revert any active n8n workflow to a previous commit, or import new n8n templates directly from the repository. This robust n8n node architecture ensures that all your automation logic is backed up and traceable.

How it Works

This comprehensive n8n workflow template operates via three primary entry points:


  1. Scheduled Synchronization (n8n to GitHub):

The Schedule Trigger initiates a full sync check.
An internal n8n node (n8n-sync-all) retrieves all active n8n workflows.
The flow splits batches and executes a sub-workflow for each item (using Sync-all-workflows).
For each n8n workflow, the system compares the live JSON with the corresponding file in GitHub (GH | Get file data).
A Check Status switch determines if the workflow is new, different, or synchronized. If different, the GH | Edit existing file n8n node updates GitHub, providing perfect version control for every change to your n8n workflow.


  1. Dashboard Generation:

The Webhook-open-dashboard acts as the primary n8n trigger for dashboard requests.
It fetches all live n8n workflows using the specialized n8n node (n8n-all-workflows) and all files from GitHub (GH | all-workflows).
The Compare Datasets n8n node then analyzes the two data streams, categorizing workflows into three states: present only in n8n, fully synced, or present only in GitHub.
The results are compiled and passed to the HTML node, which generates the dynamic dashboard view, sent back via the Respond to Webhook node.


  1. Interactive Actions (Rollback/Status Control):

The Webhook-actions n8n trigger handles user actions (e.g., activating, deactivating, or importing/rolling back an n8n workflow).
The Query action switch routes the flow. For rollback actions (importWorkflow), the flow fetches specific commit content using GitHub HTTP Requests (GH | Get commit content).
The flow then uses the specialized n8n node (either Create a workflow or Update a workflow) to push the retrieved historical JSON directly back into the running n8n instance, completing the rollback for that specific n8n workflow.

Installation Guide

To deploy this advanced n8n workflow template, follow these steps:


  1. Import: Copy the provided JSON into your n8n instance and activate the workflow.

  2. Credentials: This n8n workflow requires several credentials:

GitHub Credential: Configure a GitHub credential with read/write permissions for synchronization and updating files. Specify the target repository and branch within the relevant GitHub n8n node configurations.
n8n API Credential: Since this workflow uses the internal n8n node (type n8n-nodes-base.n8n) to manage workflows, you must set up an API credential for your self-hosted n8n instance. This credential needs sufficient permissions to list, activate, deactivate, create, and update all n8n templates.

  1. Configuration: Update the global variables or hardcoded values related to repository pathing and workflow naming conventions in the initial Globals n8n node to match your environment.

Node Details

Webhook-open-dashboard (n8n trigger): Acts as the entry point for requesting the synchronization status dashboard.
n8n (n8n node): Used extensively (e.g., n8n-all-workflows, Activate a workflow) to interact with the n8n host API. This allows the workflow to read, update, and change the activation status of other n8n workflow definitions.
GitHub (n8n node): Manages file operations in GitHub, including getting all file paths (GH | all-workflows), retrieving specific file data (GH | Get file data), and creating or editing the workflow JSON files.
Compare Datasets (n8n node): Crucial for the dashboard, this node compares the list of active n8n workflows against the list of files in GitHub to determine sync status.
Switch (n8n node): Used for advanced routing based on data values, such as identifying which user action was requested (Query action) or checking the synchronization status of an individual n8n workflow (Check Status).
HTTP Request (n8n node): Used primarily to interface with the deeper GitHub API to fetch specific file commits (GH | Get file commits) or raw commit content for rollback purposes.


  • HTML (n8n node): Renders the comparison data into a rich, interactive HTML dashboard returned to the user.

Related n8n Workflows

Paid

Nodes: 23 Nodes
Updated: December 26 2025
View all
Created by

Featured*