FTP PULL IN. GCS OUT. NO SCRIPTS.
Collect files from FTP servers into Google Cloud Storage
DocEvent polls your FTP or FTPS server on a schedule, collects new files and delivers each one into your Google Cloud Storage bucket. FTP-to-GCS ingestion with filename filtering, no scripts, and a full audit trail.
From
FTP Pull
To
GCS
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How FTP Pull to GCS routing works
Source
FTP Pull
DocEvent connects to your FTP or FTPS server on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via FTP Pull
Scheduled outbound polling of any FTP or FTPS server — nothing to install on it. Filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder. TLS certificate verification for FTPS.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to GCS
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Common use cases
Real workflows that teams automate with a FTP Pull → GCS channel.
- Archive a partner's FTP drop zone into GCS on a schedule
- Modernise legacy FTP feeds into a Google Cloud data platform
- Retire download-then-upload scripts with one managed channel
- Filename filtering, retries and a full audit trail included
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the FTP Pull or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
FTP Pull
Scheduled outbound polling of any FTP or FTPS server — nothing to install on it. Filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder. TLS certificate verification for FTPS.
DocEvent connects to your FTP or FTPS server on a schedule and collects new files.Destination:
Google Cloud Storage
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Files are delivered into your Google Cloud Storage bucket.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages