Skip to main content

Automatically transfer FTP files to Google Drive with batch processing

Workflow preview

Workflow preview
100%
Automatically transfer FTP files to Google Drive with batch processing preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

How it works This workflow automates the transfer of files from an FTP server to Google Drive. It runs on a schedule, lists files in a defined FTP directory, and processes them in batches. Each fil...

Best for

  • Content Creation automation workflows
  • File Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.ftp, n8n-nodes-base.splitinbatches, n8n-nodes-base.googledrive, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.

Original n8n.io source

1.1 Workflow description

Title
Automatically transfer FTP files to Google Drive with batch processing
Workflow name
Automatically transfer FTP files to Google Drive with batch processing

How it works

This workflow automates the transfer of files from an FTP server to Google Drive.
It runs on a schedule, lists files in a defined FTP directory, and processes them in batches.
Each file is downloaded sequentially from the FTP server and uploaded to Google Drive.
The workflow ensures filenames are preserved for consistency during the sync process.

Step-by-step

1. Trigger the workflow

  • Schedule Trigger – Starts the workflow automatically at set intervals.

2. List files from FTP

  • FTP (List Files) – Retrieves a list of files from the FTP server path.

3. Batch process files

  • Split in Batches – Breaks the file list into smaller chunks for sequential handling.

4. Download file from FTP

  • FTP (Download File) – Downloads each file from the FTP server.

5. Upload to Google Drive

  • Google Drive (Upload File) – Uploads the file to Google Drive while keeping its original filename.

Why use this?

  • Automates repetitive FTP-to-cloud transfer tasks with no manual intervention.
  • Reduces system overload by processing files in manageable batches.
  • Ensures data backup from FTP servers directly into cloud storage.
  • Maintains file structure and filenames for easy reference and retrieval.
  • Provides reliable, scheduled synchronization between FTP and Google Drive.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - ⏯️ Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - 📂 List Files from FTP

Type / Role
n8n-nodes-base.ftp - ftp
Config choices
Version 1

Block 3 - 🔀 Batch Files

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 4 - ⬇️ Download File from FTP

Type / Role
n8n-nodes-base.ftp - ftp
Config choices
Version 1

Block 5 - ☁️ Upload to Google Drive

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 6 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automatically transfer FTP files to Google Drive with batch processing
Complexity intermediate
Nodes 9
Categories Content Creation, File Management
Author Avkash Kakdiya
Published 18 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8703/8703.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automatically transfer FTP files to Google Drive with batch processing do?

How it works This workflow automates the transfer of files from an FTP server to Google Drive. It runs on a schedule, lists files in a defined FTP directory, and processes them in batches. Each fil...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, File Management use case.