n8n Backup & Disaster Recovery: Save the Structures, Rot the Secrets, Keep the Key Apart

Description and use

Separating workflow exports from the encryption key and database, and conducting regular recovery drills, prevents irreversible data loss in a disaster.

Problem

Self‑hosted n8n instances lose workflow definitions, encrypted credentials, and the encryption key in a disaster, making recovery impossible.

Outcome

Separating workflow exports from the encryption key and database, and performing regular recovery drills, ensures that a disaster does not result in irreversible data loss.

Workflow

• 1. Configure a nightly job to export workflows via the n8n CLI, producing JSON files.
• 2. Pipe the export through a secret‑scrubbing step to remove hardcoded tokens and sensitive data.
• 3. Store the scrubbed export files in a versioned backup system (e.g., Git or object storage).
• 4. Use infrastructure snapshot tooling to back up the n8n database and the N8N_ENCRYPTION_KEY, storing them separately from the exports.
• 5. Quarterly, spin up a fresh n8n instance on staging, restore the database and key, import the scrubbed workflow exports, and run a test end‑to‑end execution to validate recovery.
• 6. Monitor the export job with a heartbeat ping; alert on silence to detect failed backups.
• 7. Before each deploy, run the free n8n workflow audit tool to detect secret patterns, localhost URLs, and broken references in the export.

Evidence

CLI exports produce JSON of workflow structures: perfect for version history and Git-based backup.

Source

Item two: the database plus N8N_ENCRYPTION_KEY, via your infra provider's snapshot tooling, stored somewhere the exports aren't.

Source

Quarterly, minimum: fresh n8n on staging, feed it the backup database and key, import workflows, light one real execution end-to-end.

Source