Dynamic GitHub Version Control for Automation - n8n Workflow

• Automation specialists requiring version control for their projects.
• DevOps teams managing production and staging n8n templates.
• Users who need to compare differences between their live n8n workflow and its remote GitHub backup.
• Developers looking for robust change management tools for their n8n projects.

Managing changes to crucial automation logic can be challenging without proper version control. This complex n8n workflow solves this by acting as a version control interface, specifically linking your active n8n workflows directly to GitHub. It uses multiple n8n trigger webhooks to handle four key operations: listing available flows, fetching workflow status, comparing local changes against GitHub, and committing updates. By leveraging the n8n node, this solution retrieves live workflow data, packages it, and then utilizes the GitHub n8n node to manage file operations (reads and commits), creating a seamless and auditable development environment for your n8n templates.

This powerful n8n workflow operates across four distinct operational branches, each initiated by a dedicated n8n trigger webhook:

1. UI Generation (Listing GitHub Workflows): A webhook trigger (Webhook-ideogener8r) captures the request. The flow sets necessary variables and uses the GitHub n8n node to fetch a list of workflow files. This data is aggregated and passed to the HTML-UI n8n node, which renders a functional user interface, responding via the Respond with UI n8n node.


2. Workflow Comparison: The Get-Workflow-Changes webhook initiates a comparison. The flow first retrieves the specified workflow JSON from GitHub using the GitHub n8n node. It then uses the Get n8n Workflow n8n node to fetch the live definition of the same n8n workflow from the local instance. A subsequent Code n8n node (ComapreNodes) executes the logic to highlight differences, and the result is returned via a webhook response.


3. Local Workflow Listing: The Get-n8n-workflows trigger uses the n8n | get wf1 n8n node to retrieve a list of all active n8n templates on the instance. This list is processed and returned via a webhook for display in the control panel.


4. Committing Changes: The submit-form webhook handles saving updates. It determines whether the user is editing an existing workflow or creating a new one via the Switch1 n8n node. Both paths use an n8n node to retrieve the current workflow content before passing it to the appropriate GitHub n8n node (Commit Workflow Edit or Commit New File) to finalize the version control process. Every commit uses the GitHub n8n node to ensure synchronization between the live n8n workflow and the remote repository.

To deploy this comprehensive n8n workflow:

1. Import: Copy the provided JSON data and paste it into your n8n instance using the 'New' -> 'Import from JSON' function.


2. Credentials: You will need to set up two main sets of credentials:

1. Webhook URLs: After activation, retrieve the Webhook URLs for all four n8n trigger nodes (Webhook-ideogener8r, Get-Workflow-Changes, Get-n8n-workflows, and submit-form). These URLs are used by the front-end UI components that drive this version control system.


2. Configure Paths: Adjust the parameters in the various Set n8n node instances (e.g., Set Workflow Variables, Set GH Repo and Path3) to point to your specific GitHub repository name and desired file paths for saving your n8n workflow files.

Webhook (Multiple Triggers): Acts as the entry point (n8n trigger) for the UI interaction, comparison requests, and commit submissions.
Set n8n node: Used extensively (e.g., Set Workflow Variables, Set Flows) to extract, rename, and set variables like repository name, file paths, and workflow IDs needed for subsequent GitHub and n8n node operations.
n8n node (e.g., n8n | get wf1, Get n8n Workflow): Essential for communication with the n8n API itself. The primary function is to list all existing n8n workflows (getAll) or fetch the JSON definition of a specific n8n workflow (get) based on its ID.
GitHub n8n node: Handles all version control operations, including listing files in the repository, reading the content of a stored n8n workflow file, and committing new or edited workflow JSON back to the repository.
HTML n8n node: Used in the initial flow (HTML-UI) to dynamically generate and serve the user interface that interacts with the other webhook endpoints, effectively creating a dedicated UI for managing the n8n templates.
Respond to Webhook n8n node: Returns data (HTML UI, comparison results, or commit confirmations) back to the user or requesting client after the execution of the n8n workflow path.

• Switch n8n node (Switch1): Determines the execution path during a submission, distinguishing between updating an existing n8n workflow file and creating a new one in the GitHub repository.