N8N Workflow Backup to GitHub

Name: N8N Workflow Backup to GitHub
Rating: 5 (5 reviews)
Author: Free N8N

Intermediate

16 nodes connected

detail.loadingPreview

Free N8N Temples

114 views

0 downloads

Automationbackupgithubn8nversion control

Automate backing up your N8N workflows to a GitHub repository.

About This Workflow

This workflow automates the process of backing up your N8N workflows to a specified GitHub repository. It checks for existing workflow files in GitHub, compares them with the current N8N workflows, and either updates existing files or creates new ones, ensuring your workflow configurations are version-controlled.

Key Features

Automated Backup: Schedule daily backups of your N8N workflows.
Version Control: Store workflow JSON files in a GitHub repository.
Conflict Detection: Compares existing GitHub files with N8N workflows to detect differences.
Conditional Operations: Updates existing files if they differ or creates new ones if they don't exist.
Configurable Repository: Easily set the GitHub owner, repository name, and path.

How To Use

Manual Trigger or Schedule: The workflow can be triggered manually by clicking 'execute' or scheduled to run daily at 20:00.
Set Globals: Configure the Globals node with your GitHub repository details:
- repo.owner: The owner of the GitHub repository.
- repo.name: The name of the GitHub repository.
- repo.path: The path within the repository where workflows will be stored (e.g., my-team/n8n/workflows/).
Fetch N8N Workflows: The N8N Workflows node fetches a list of all your N8N workflows from the local N8N instance.
Process Workflows Individually: The dataArray node restructures the fetched data, and OneAtATime ensures each workflow is processed individually.
Fetch GitHub File: The GitHub node attempts to retrieve the corresponding workflow file from your GitHub repository based on the workflow name.
Get N8N Workflow Detail: The N8N Workflow Detail node fetches the full details of the current N8N workflow.
Compare and Determine Status: The isDiffOrNew function node compares the content of the GitHub file (if it exists) with the current N8N workflow data. It determines if the workflow is same, different, or new.
Route Based on Status: The github_status switch node directs the execution based on the comparison result:
- same: No action is taken (connected to same NoOp node, which then proceeds to OneAtATime to continue processing).
- different: The GitHub Edit node is used to update the existing file in the GitHub repository.
- new: The GitHub Create node is used to create a new file in the GitHub repository.
Execute GitHub Operation: The GitHub Edit or GitHub Create nodes perform the respective file operation in your GitHub repository. The OneAtATime node is then re-entered to continue processing the next workflow in the batch.
Credentials: Ensure you have configured your GitHub API credentials (named 'GitHub') in N8N.

Apps Used

backup

github

n8n

version control

Workflow JSON

{
  "id": "c8fb7096-fd8f-4b83-be03-f9681f1db830",
  "name": "N8N Workflow Backup to GitHub",
  "nodes": 16,
  "category": "Automation",
  "status": "active",
  "version": "1.0.0"
}

Note: This is a sample preview. The full workflow JSON contains node configurations, credentials placeholders, and execution logic.