Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
This n8n workflow template uses community nodes and is only compatible with the self hosted version of n8n. Title: n8n Credentials and Workflows Backup on Change Detection Purpose: Never lose track...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.executeworkflow, n8n-nodes-base.readwritefile, n8n-nodes-base.set, n8n-nodes-base.executecommand, n8n-nodes-base.extractfromfile, n8n-nodes-base.crypto, n8n-nodes-base.executeworkflowtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Hamed Nickmehr.
Original n8n.io sourceThis n8n workflow template uses community nodes and is only compatible with the self-hosted version of n8n.
Title: n8n Credentials and Workflows Backup on Change Detection
Purpose: Never lose track of your n8n changes again! This workflow smartly backs up all your workflows and credentials, automatically detects any changes using hash comparison, and pushes updates to GitHub—but only when something has actually changed. Set your own interval and stop cluttering your repo with redundant commits.
Trigger:
Workflow Backup Process:
Set Workflow Path: Defines the local backup file path for workflows.
Get Old Workflow Hash: Executes a helper workflow to retrieve the previous hash.
Execute Workflow Backup: Runs n8n export:workflow to export all workflows to the defined file path.
Get New Workflow Hash: Executes a helper workflow to generate the new hash from the exported file.
Compare Hashes (If Workflow Updated): Checks if the new hash differs from the old one.
If Updated:
Credential Backup Process:
Set Credential Path: Defines the local backup file path for credentials.
Get Old Credential Hash: Executes a helper workflow to retrieve the previous hash.
Execute Credential Backup: Runs n8n export:credentials to export all credentials.
Get New Credential Hash: Executes a helper workflow to generate the new hash from the exported file.
Compare Hashes (If Credential Updated): Checks for changes.
If Updated:
Hash Generator (Helper Flow): Used in both workflow and credential backup paths:
GitHub Integration:
https://github.com/your-github-name/n8n-onchange-bachupbackups/WorkFlow Backup -timestamp-.json and backups/Credential Backup -timestamp-.jsonChange Detection Logic:
Error Handling:
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automatic workflow & credentials backup to GitHub with change detection |
|---|---|
| Complexity | advanced |
| Nodes | 21 |
| Categories | DevOps |
| Author | Hamed Nickmehr |
| Published | 02 Jun 2025 |
Use the JSON export at /data/workflows/4609/4609.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This n8n workflow template uses community nodes and is only compatible with the self hosted version of n8n. Title: n8n Credentials and Workflows Backup on Change Detection Purpose: Never lose track...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.