n8n Credentials Backup to GitHub

• Automated Backups: Triggers backups automatically on a schedule (e.g., every 2 hours) or manually.
• GitHub Integration: Leverages the GitHub API to read existing credential files and create or update them.
• File Versioning: Stores credentials as individual JSON files named by their n8n credential ID within a specified folder in your GitHub repository.
• Difference Detection: Compares existing credentials with the current ones to determine if they are 'new', 'different', or 'same', and acts accordingly.
• Configurable Repository: Easily set your GitHub username, repository name, and the path within the repository where credentials should be stored via the 'Globals' node.
• Secure Storage: Backs up decrypted credentials, making them readily available for recovery.

Setup Guide

1. Configure GitHub Credentials: In n8n, go to Credentials and add a GitHub API credential. Ensure it has the necessary permissions to read and write files in your target repository.

2. Update Globals Node: Locate the Globals node in the workflow. Update the following parameters:

   • repo.owner: Your GitHub username.
   • repo.name: The name of your GitHub repository.
   • repo.path: The folder path within your repository where you want to store the credential files. If the folder doesn't exist, it will be created. Example: credentials/.

3. Trigger the Workflow:

   • Manual Trigger: Click the 'execute' button on the On clicking 'execute' node.
   • Scheduled Trigger: The Schedule Trigger node is configured to run every 2 hours by default. You can adjust this schedule as needed.

4. Workflow Execution:

   • The workflow first executes a command-line command (npx n8n export:credentials --all --decrypted) to get the current credentials from the n8n instance.
   • It then formats the output JSON.
   • The Loop Over Items node processes each credential.
   • For each credential, the workflow attempts to get the corresponding file from GitHub using the Get file data node.
   • The isDiffOrNew node compares the fetched data with the current credentials.
   • Based on the comparison, it either does nothing (Same file - Do nothing), updates the file in GitHub (Edit existing file for 'different' status), or creates a new file in GitHub (Create new file for 'new' status).
   • The Return node signifies the completion of a branch of operations.