Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 13 nodes and runs on a schedule (every day at 02:00). Along the way it connects AWS S3, S3, Azure Storage and Google Cloud Storage.
How it runs
Trigger: On a schedule (every day at 02:00).
- List Objects (AWS S3): get many
- Path Extraction (Split Out): splits a list into separate items
- Download Objects (AWS S3): uses AWS S3
- Upload Objects to MinIO (S3): upload
- BLOB Listing (Azure Storage): work with blob
- Path extraction (Split Out): splits a list into separate items
- BLOB Download (Azure Storage): get (blob)
- MinIO BLOB Upload (S3): upload
- Object Listing (Google Cloud Storage): work with object
- Path extraction (Split Out): splits a list into separate items
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Split Out
n8n-nodes-base.splitOut - Schedule Trigger
n8n-nodes-base.scheduleTrigger - AWS S3
n8n-nodes-base.awsS3 - S3
n8n-nodes-base.s3 - Azure Storage
n8n-nodes-base.azureStorage - Google Cloud Storage
n8n-nodes-base.googleCloudStorage
From the author
Automated AWS S3 / Azure / Google to local MinIO Object Backup with Scheduling What this workflow does ? This workflow performs automated, periodic backups of objects from an AWS S3 bucket, an Azure Container or a Google Storage Space to a MinIO S3 bucket…