Automated Google Drive to FTP transfer with JSON logging & reports
Needs changesWhat this workflow does
This workflow has 14 nodes and runs on a schedule (every 6 hours) (plus 1 other trigger). Along the way it connects Google Drive.
How it runs
Trigger: On a schedule (every 6 hours) (plus 1 other trigger).
- Get Drive Files (Google Drive): search
- Filter & Validate Files (Code): runs custom JavaScript code
- Process One by One (Loop Over Items (Split in Batches)): loops over the items in batches
- Download from Drive (Google Drive): download
- Create Final Report (Code): runs custom JavaScript code
- Upload to FTP (FTP): uses FTP
- Save Notes JSON (Write Binary File): uses Write Binary File
- Update Notes - Success (Code): runs custom JavaScript code
- Upload Notes to Drive (Google Drive): uses Google Drive
- Check if More Files (If): checks a condition and branches into true / false
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Write Binary File in Save Notes JSON: replace with Read/Write Files from Disk.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Write Binary File Save Notes JSON | Read/Write Files from Disk |
Nodes used (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Drive
n8n-nodes-base.googleDrive - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - FTP
n8n-nodes-base.ftp - If
n8n-nodes-base.if - Write Binary File
n8n-nodes-base.writeBinaryFile - Send Email
n8n-nodes-base.emailSend - Webhook
n8n-nodes-base.webhook
From the author
Google Drive to FTP Transfer Workflow - Setup Guide Overview This n8n workflow automatically transfers files from Google Drive to an FTP server on a scheduled basis. It includes comprehensive logging, email notifications, and error handling. Features -…