Scheduled FTP to Google Drive File Synchronization with Batching - n8n Workflow

System administrators needing scheduled file backups or data mirroring. Users requiring reliable, automated data migration between an FTP host and cloud storage. Developers looking for robust, production-ready file transfer n8n workflow examples. Anyone seeking high-efficiency n8n templates for managing large volumes of cloud storage operations.

This automated n8n workflow solves the critical business challenge of maintaining file parity between legacy FTP systems and modern cloud storage solutions like Google Drive. By utilizing a scheduled n8n trigger, the process runs completely unattended, reducing manual effort and ensuring timely data synchronization. The core intelligence of this n8n template lies in its robust handling of large file lists: it employs the Split In Batches n8n node to process files sequentially, preventing bottlenecks and increasing the reliability of the overall n8n workflow. This is a must-have n8n node combination for stable, high-volume file transfers.

1. Trigger Initiation: The n8n workflow is activated by the Schedule Trigger n8n node at set intervals (e.g., daily, hourly).


2. File Listing: The List Files from FTP n8n node connects to the specified remote server and retrieves the metadata for all files in the defined source directory.


3. Flow Control: The Batch Files n8n node (Split In Batches) takes the list of files and organizes them into individual processing units. This is crucial for handling large lists safely within the n8n workflow execution.


4. Download: For each item in the batch, the Download File from FTP n8n node executes. It dynamically references the file name using the n8n expression {{ $json.name }} to fetch the corresponding binary data.


5. Upload: Finally, the Upload to Google Drive n8n node receives the binary data and transfers the file to the configured Google Drive folder. It uses the same dynamic n8n expression to ensure the file retains its original name, successfully completing this iteration of the n8n workflow.

1. Import: Copy the provided JSON and import it directly into your n8n instance using the 'New' button or the 'Import Workflow' option.


2. FTP Credentials: Locate the List Files from FTP n8n node and the Download File from FTP n8n node. Update the 'ftp_credentials' placeholder with your actual FTP server credentials (Host, User, Password).


3. Google Drive Credentials: Locate the Upload to Google Drive n8n node. Create or select an OAuth2 credential for Google Drive API access. This n8n node requires permissions to upload files.


4. Configuration: Adjust the path parameter in the List Files from FTP n8n node (/path/to/your/files) and select the target folder in the Upload to Google Drive n8n node.


5. Scheduling: Configure the Schedule Trigger n8n trigger to define how frequently the sync should run.


6. Activate: Set the n8n workflow to 'Active' to start the scheduled synchronization.

Schedule Trigger (n8n trigger): The starting n8n node, responsible for running the entire operation on a recurring basis.
FTP (List Files from FTP n8n node): Operation set to List. Requires FTP credentials and a specific remote path to analyze.
Split In Batches (Batch Files n8n node): A core flow control n8n node. Ensures that the list of files is processed sequentially to maintain system stability and avoid timeouts.
FTP (Download File from FTP n8n node): Operation set to Download. Uses dynamic data {{ $json.name }} derived from the listing step to specify which file to retrieve.

• Google Drive (Upload to Google Drive n8n node): Operation set to Upload. Uses dynamic data {{ $json.name }} for the uploaded file name, ensuring consistency with the source. This final n8n node requires Google Drive OAuth credentials.