How to Back Up and Restore n8n Workflows Safely

n8n workflows can be exported as JSON for quick copying or versioning, but a workflow file is not a complete instance backup. A recoverable self-hosted backup may also need the database, credential-encryption key, binary data, configuration, and custom or community nodes.

Use the manual method below for a single workflow. Use a database- and host-level backup plan when you need disaster recovery for the entire n8n installation.

Back up one workflow from the n8n editor

1. Save and open the workflow

Open the workflow you want to protect and save its latest changes. Record the n8n version and any required community nodes if the workflow depends on them.

2. Download the workflow JSON

Open the workflow menu in the upper-right corner and choose Download. n8n saves the current workflow as a JSON file.

3. Store the export with useful metadata

Use a consistent filename such as customer-onboarding_2026-08-12.json. Store it in a protected backup location rather than leaving the only copy in Downloads.

Exported workflow JSON can contain node configuration, expressions, URLs, code, and credential names or IDs. It does not provide the underlying credential secrets, but the remaining configuration may still reveal sensitive architecture. Review the file before placing it in a repository or sharing it.

Restore a workflow JSON file

Create or open the target workflow, open its menu, and choose Import from File.

Select the saved JSON file and open it.

After import, reconnect credentials, verify environment variables and sub-workflows, inspect nodes marked outdated or missing, and run the workflow with safe test data. Importing a JSON file should not be treated as proof that the workflow is operational.

Back up all workflows on a self-hosted instance

For self-hosted n8n, the CLI can export workflows into separate files:

n8n export:workflow --backup --output=backups/

Run the command in the same environment and with access to the same n8n configuration and database as the instance. The exact container command or path depends on how n8n is deployed. See the official n8n CLI documentation for current options.

Recent n8n versions also support workflow export/import packages for preserving related project and folder references. Check the current export and import documentation before choosing a format.

What a full n8n backup must cover

n8n generates and stores an encryption key for credentials unless you supply one. Back up that key securely and separately from routine workflow exports. The n8n encryption-key guide explains its role.

Automate backups without creating a single point of failure

Schedule the backup from the host, container platform, or an independent backup service when possible. A workflow running inside the same n8n instance cannot back anything up if that instance or its database is unavailable.

1. Create a consistent database snapshot using the method recommended for your database.
2. Export workflow files if you also want human-readable or versionable copies.
3. Copy the backup to an encrypted destination separate from the n8n host.
4. Apply retention rules so that accidental corruption or deletion does not immediately replace every good copy.
5. Monitor job failures and available storage.

A private Git repository can be useful for reviewed workflow JSON files, but do not commit credential exports, encryption keys, database dumps, or unreviewed files containing sensitive URLs or code. For server-side storage options, compare these open-source Linux backup utilities.

Test the restore process

• Restore into an isolated test environment, not production.
• Use the same n8n version first, then test upgrades separately.
• Confirm that credentials decrypt and required nodes are installed.
• Disable production triggers while testing.
• Run representative workflows with non-production data.
• Record the recovery steps and the time required.

If restoring reveals broader platform limitations, TipsMake also compares alternatives to n8n.

Minimum backup checklist

• Workflow exports are current and readable.
• The database and encryption key are both protected.
• Backups exist outside the n8n host.
• Retention includes more than the latest copy.
• A recent restore test succeeded.
• Access to backup locations is limited and logged.