n8n Workflow: SSH rclone Backup to Backblaze B2 (B2 Sync)

Back up a server folder to Backblaze B2 on a schedule—optionally encrypted with rclone crypt

This n8n workflow connects to your source server via SSH, installs rclone if needed, and automatically backs up a chosen directory to your Backblaze B2 bucket on a schedule. You can run it in sync (mirroring) mode or versioned copy mode—and optionally encrypt data using an rclone crypt remote.

What this workflow does

• Collects backup settings via an n8n Form trigger and stores the configuration in an n8n Data Table.
• Connects to the source server over SSH and ensures rclone is available (it may install it using sudo).
• Creates an rclone Backblaze B2 remote using your provided B2 Key ID and Application Key (bucket-level read/write access).
• Optional encryption: if you enable it, the workflow adds an rclone crypt remote using the provided passphrase.
• Scheduled execution: on each schedule run, it loads the saved configuration and tests the rclone connection over SSH. If the credentials or bucket are invalid, the workflow stops with an error.
• Backup modes:
  • Sync: mirrors the source directory to Backblaze B2 using rclone sync.
  • Versioned: copies the source directory into a timestamped folder using rclone copy.

Use cases

• Automate offsite backups from a Linux server to Backblaze B2 without manual rclone runs.
• Run “mirrored” backups for straightforward disaster recovery, or choose “versioned” snapshots to keep historical copies.
• Add encryption-by-default with rclone crypt for safer backups to cloud storage.

Technical details

• n8n nodes used: if, ssh, code, data table, sticky note, form trigger.
• Transport: SSH to the source server; rclone commands run remotely.
• Backends: Backblaze B2 via rclone (optionally wrapped by rclone crypt).
• Requires: SSH access with an SSH key and passwordless sudo if rclone must be installed.