The flow
Starts it 1Logic 3Service 9
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2BLOB ListingAzure StorageService
- 3Object ListingGoogle Cloud StorageService
- 4List ObjectsAws S3Service
- 5Path extractionSplit OutLogic
- 6Path extraction1Split OutLogic
- 7Path ExtractionSplit OutLogic
- 8BLOB DownloadAzure StorageService
- 9Download Objects DataGoogle Cloud StorageService
- 10Download ObjectsAws S3Service
- 11MinIO BLOB UploadS3Service
- 12Upload on MinIOS3Service
- 13Upload Objects to MinIOS3Service
How it's built
- Starts on
- A clock
- Steps
- 13
- Size
- Medium: a working afternoon
- Connects to
- Google Cloud Storage, S3
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Cloud Storage and S3 accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 13 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 13 steps before you point it at anything that matters.