Automated File Synchronization from FTP Server to Google Drive - n8n Workflow

System Administrators requiring reliable backup and synchronization solutions.
Businesses looking to migrate legacy FTP data to modern cloud storage solutions.
Developers and power users seeking robust, ready-to-use file transfer n8n templates.
Anyone needing an automated, scheduled file movement solution using an n8n workflow.

Manually moving files between traditional systems like FTP and cloud platforms like Google Drive can be tedious and resource-intensive. This powerful n8n workflow eliminates manual intervention by creating a smooth, automated pipeline for data transfer.

This specific n8n workflow is configured with a Manual Trigger, making it ideal for testing or on-demand execution, though it is easily adapted to use a time-based n8n trigger (like Cron) for scheduled synchronization. It intelligently uses the If n8n node to filter out directories, ensuring that only actual file data is downloaded and uploaded. By leveraging specific n8n node operations for listing, downloading, and cloud uploading, this solution exemplifies how the n8n platform can streamline complex file operations into a simple, automated n8n workflow.

The execution of this file synchronization n8n workflow follows a logical four-step sequence:

1. Initiation (n8n trigger): The automation starts via the Manual Trigger n8n node. This simple n8n trigger can be replaced by any other node type (e.g., webhook or schedule) depending on your operational needs.


2. FTP Listing: The next n8n node uses the FTP service credentials to connect to the server and list all contents found in the specified root path (/). This generates a list of potential files and folders.


3. Conditional Filtering and Download: The flow splits using an If n8n node, which serves as crucial flow control. It filters the items to ensure the type property is equivalent to a file (-). If the condition is met, the file is routed to the dedicated FTP n8n node that handles the binary download, using dynamic expressions ({{ $json.path }}) to specify the correct file.


4. Google Drive Upload: The final step involves the Google Drive n8n node. This node receives the binary file data and uploads it directly to the pre-configured destination folder ID on Google Drive, concluding the transfer for that item within the overall n8n workflow.

To deploy and utilize this file transfer n8n workflow template, follow these setup instructions:

1. Import: Copy the provided JSON code and import it directly into your self-hosted or cloud n8n instance.


2. Configure FTP Credentials: Open the "List FTP Directory" and "Download File from FTP" n8n node blocks. Create new FTP credentials, providing the required server address, username, and password for your source FTP server.


3. Configure Google Drive Credentials: Select the "Upload to Google Drive" n8n node. Establish or select your existing Google Drive OAuth2 credentials, ensuring the scope allows for file management.


4. Set Target Folder ID: In the "Upload to Google Drive" n8n node, navigate to the parameters and replace the placeholder folderId with the actual ID of the Google Drive folder where you wish to store the synchronized files.


5. Test Execution: Click the Execute button on the Manual Trigger n8n trigger to verify that the entire n8n workflow runs correctly and files are transferred as expected.

This n8n workflow relies on the following key n8n node configurations:

Manual Trigger (n8n trigger):
Function: Acts as the starting point, allowing manual execution of the n8n workflow.
Key Configuration: Simple start mechanism.
List FTP Directory (FTP n8n node):
Function: Initiates connection to the FTP server and retrieves a list of directory contents.
Key Configuration: Operation: List; Path: / (Root directory).
Filter Files Only (If n8n node):
Function: A core logic component ensuring only file objects (and not folders) proceed to the download stage.
Key Configuration: Condition: {{ $json.type }} equals -.
Download File from FTP (FTP n8n node):
Function: Downloads the actual binary data for each file item approved by the preceding n8n node.
Key Configuration: Path: {{ $json.path }}; Binary Property Name: {{ $json.name }}.
Upload to Google Drive (Google Drive n8n node):
Function: Receives the binary file data and uploads it to the chosen folder on Google Drive.
* Key Configuration: Operation: Upload File. Requires setting a specific folderId destination. This n8n node completes the primary task of the n8n workflow.