Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Automated n8n Workflows & Credentials Backup to Local/Server Disk & FTP Complete backup solution that saves both workflows and credentials to local/server disk with optional FTP upload for off site...
n8n-nodes-base.stickynote, n8n-nodes-base.code, n8n-nodes-base.readwritefile, n8n-nodes-base.emailsend, n8n-nodes-base.executecommand, n8n-nodes-base.scheduletrigger, n8n-nodes-base.converttofile, n8n-nodes-base.n8n
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Florent.
Original n8n.io sourceComplete backup solution that saves both workflows and credentials to local/server disk with optional FTP upload for off-site redundancy.
What makes this workflow different:
Backup Process (Automated Daily at 4 AM):
Initial Setup:
Configure the Init Node - Open the "Init" node and customize these key parameters in the "Workflow Standard Configuration" section:
// Admin email for notifications
const N8N_ADMIN_EMAIL = $env.N8N_ADMIN_EMAIL || '[email protected]';
// Workflow name (auto-detected)
const WORKFLOW_NAME = $workflow.name;
// Projects root directory on your server
const N8N_PROJECTS_DIR = $env.N8N_PROJECTS_DIR || '/files/n8n-projects-data';
// projects-root-folder/
// └── Your-project-folder-name/
// ├── logs/
// ├── reports/
// ├── ...
// └── [other project files]
// Project folder name for this backup workflow
const PROJECT_FOLDER_NAME = "Workflow-backups";
Then customize these parameters in the "Workflow Custom Configuration" section:
// Local backup folder (must exist on your server)
const BACKUP_FOLDER = $env.N8N_BACKUP_FOLDER || '/files/n8n-backups';
// FTP backup folder (root path on your FTP server)
const FTP_BACKUP_FOLDER = $env.N8N_FTP_BACKUP_FOLDER || '/n8n-backups';
// FTP server name for logging (display purposes only)
const FTPName = 'Synology NAS 2To';
These variables can also be set as environment variables in your n8n configuration.
Set Up Credentials:
Configure Backup Folder:
Customize Email Settings:
Enabling FTP Upload (Optional):
By default, FTP upload nodes are disabled for easier setup. To enable off-site FTP backups:
Simply activate these 4 nodes (no other changes needed):
Configure FTP credentials in the two upload nodes
The workflow will automatically handle FTP operations and include upload status in reports
This automated backup workflow saves your n8n data to both local disk and FTP server. To restore your backups, use:
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 28 workflow blocks. Download the JSON for the full node graph.
| Workflow | Complete backup solution for n8n workflows & credentials (local/FTP) |
|---|---|
| Complexity | advanced |
| Nodes | 28 |
| Categories | DevOps |
| Author | Florent |
| Published | 01 Oct 2025 |
Use the JSON export at /data/workflows/9151/9151.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Automated n8n Workflows & Credentials Backup to Local/Server Disk & FTP Complete backup solution that saves both workflows and credentials to local/server disk with optional FTP upload for off site...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.