Automated FTP to Google Drive Synchronization - n8n Workflow

System Administrators requiring scheduled data backup from legacy FTP servers.
Data Engineers needing to migrate files to cloud storage automatically.
Users looking for reliable, hands-off file synchronization using pre-built n8n templates.
Anyone utilizing n8n to connect diverse data silos.

Managing files across self-hosted FTP servers and cloud platforms like Google Drive can be tedious and prone to manual error. This robust n8n workflow eliminates that inefficiency by automating the entire synchronization process. By leveraging the flexibility of the n8n node architecture, this solution ensures that large quantities of files are handled sequentially and reliably using batch processing. This specific n8n workflow solves the common problem of reliable bulk transfer, providing a set-and-forget mechanism initiated by an n8n trigger, ensuring your cloud storage remains updated with the latest files from your FTP source.

This automation operates on a loop, starting with the scheduled n8n trigger and systematically processing every file found on the remote FTP server.

1. Scheduled Execution: The process begins with the ⏯️ Schedule Trigger n8n node, set to run at defined intervals.


2. File Listing: The 📂 List Files from FTP n8n node connects to the specified FTP server credentials and path, retrieving a complete list of files and metadata available for synchronization.


3. Batch Processing: The list of files is then routed to the 🔀 Batch Files n8n node. This crucial step splits the file list into individual items, ensuring that the heavy operations (downloading and uploading) are performed sequentially for each file, preventing timeouts or system overload—a hallmark of reliable n8n templates.


4. Sequential Download: For each batch item, the ⬇️ Download File from FTP n8n node executes, using the file name data ($json.name) passed from the previous step to download the file content into the n8n buffer.


5. Cloud Upload: Finally, the downloaded file is passed to the ☁️ Upload to Google Drive n8n node. This node uses the original filename to upload the data to the configured Google Drive folder, completing the synchronization for that specific file. The n8n workflow then loops back until all files in the batch are processed.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Copy the provided JSON code and import it into your n8n instance via the 'New' menu > 'Import from JSON'.


2. FTP Credentials Setup: Locate the 📂 List Files from FTP and ⬇️ Download File from FTP n8n nodes. You must create or select an existing FTP credential set containing the host, port, username, and password for your source server.


3. Google Drive Credentials Setup: Locate the ☁️ Upload to Google Drive n8n node. Set up or select an existing Google Drive OAuth2 credential. Ensure the credentials have the necessary scope to upload files to your target drive.


4. Configuration:

1. Activation: Set the desired schedule in the ⏯️ Schedule Trigger n8n node, then activate the n8n workflow.

⏯️ Schedule Trigger (n8n trigger):
Function: Starts the n8n workflow automatically at recurring intervals. This ensures continuous synchronization without manual intervention.
Key Configuration: Scheduled rule parameters (not defined in the default JSON but must be set by the user).
📂 List Files from FTP (FTP n8n node):
Function: Connects to the FTP server using defined credentials and retrieves a list of files and folders from the source directory.
Key Configuration: Operation: List, Path: /path/to/your/files.
🔀 Batch Files (Split In Batches n8n node):
Function: Splits the incoming list of files into manageable batches (typically one item per batch), forcing subsequent steps to run sequentially for high reliability.
Key Configuration: Defaults ensure sequential item processing.
⬇️ Download File from FTP (FTP n8n node):
Function: Downloads the content of the file specified by the batch item. This n8n node uses a dynamic expression to identify the file.
Key Configuration: Path: {{ $json.name }} (Uses the filename from the list node).
☁️ Upload to Google Drive (Google Drive n8n node):
Function: Takes the downloaded binary file content and uploads it to the chosen Google Drive destination.
* Key Configuration: Name: {{ $json.name }} (Retains original filename), Drive ID and Folder ID must be set.