Back up n8n workflows to your own Git repo.
Git is the right home for workflow history — but exporting n8n JSON by hand and scrubbing secrets every time never actually happens. Keel does it automatically on every change.
Manual git backup doesn't stick
Committing workflow JSON to git by hand is fine once. Across many workflows it stops happening — and raw n8n exports are noisy and can contain hardcoded secrets you don't want in your repo history.
How Keel's git backup works
Auto-commit on change
When a workflow changes, Keel commits its redacted JSON to your GitHub or GitLab — no manual export step.
Secrets stripped first
Redaction runs on the agent before the commit, so API keys, tokens, and webhook secrets never enter your git history.
Clean, diffable history
Stable file paths per workflow mean git diffs are readable, not a churn of position noise.
Your repo, your control
It's your GitHub/GitLab — you own the history and can use it however you like.
Find out what changed before your client does.
Keel runs a lightweight agent next to your n8n — snapshots, diffs, alerts, and rollback, with your secrets and API key never leaving your box. Free forever on one instance.
Questions
Does it commit my credentials to git?
No. Keel redacts secrets on the agent before committing, and your n8n API key never leaves your server at all.
GitHub and GitLab both?
Yes — both are supported, committing to a repo you own.
How is this better than exporting JSON myself?
It's automatic (on every change, not when you remember), redacted, and produces clean diffs instead of noisy raw exports.
See every change before it breaks a client.
Point Keel at your n8n estate this week. Free 14-day trial, no card, your keys never leave your infrastructure.