Why?
Why? Have you ever updated your n8n instance, or moved from one instance to the other and lost all your workflows? I suggest NOT DOING THAT! Especially if you have very complex workflows that would take days to recreate. Make sure you have a backup process in place! How it works Get all workflows from an n8n instance using your n8n API Formats the workflows cleanly Creates a backup package Checks if target GitHub repository exists, if not creates it Uploads a manifest Uploads a readme Uploads your workflows as separate JSON files Sends a summary to your choice (Telegram or GMAIL) What it does Backs up all your workflows Splits them out into separate JSON files for each workflow Sends a notification What it doesn't do Does not back up credentials (not smart for security reasons) Does not delete old backups Requirements n8n n8n API setup with credentials stored in instance you are running this from GitHub user & API (with repository rights) setup (API key in Github, Credentials in n8n) Future Updates If I get requests for these features I would build them: Rolling backups (delete further back than 3 days) Logic to skip the backup if nothing changed. An n8n automation workflow template by Builds.Cool.
Builds.Cool
web
paid
Others in the same category, ranked by how often they are opened.
