Deliver files from Google Cloud Storage to FTP servers
DocEvent polls your Google Cloud Storage bucket on a schedule, collects new files and pushes each one to your FTP server. No Pub/Sub, no scripts — just a service-account key, filename filtering and a full audit trail.
From
GCS Blob Pull
To
FTP
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blob / Datalakepull
Azure Filespull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How GCS Blob Pull to FTP routing works
Source
Google Cloud Storage
DocEvent checks your Google Cloud Storage bucket on a schedule and collects new blobs — no Pub/Sub or notifications needed.
DocEvent Channel
routes · retries · logs
Destination
FTP Server
Files are pushed to any FTP server you configure.
1
File arrives via GCS Blob Pull
Scheduled polling of a Google Cloud Storage bucket using a service-account key. Collects blobs from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No Pub/Sub, no bucket notifications, no event plumbing.
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 FTP
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Common use cases
Real workflows that teams automate with a GCS Blob Pull → FTP channel.
- Push GCS-processed output to trading partner FTP drop zones
- Bridge Google Cloud Storage to legacy FTP-only systems
- Collect partner uploads from a GCS bucket and republish over FTP
- Retire hand-rolled gsutil-and-cron scripts with a managed schedule
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the GCS Blob Pull or FTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Google Cloud Storage
Scheduled polling of a Google Cloud Storage bucket using a service-account key. Collects blobs from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No Pub/Sub, no bucket notifications, no event plumbing.
DocEvent checks your Google Cloud Storage bucket on a schedule and collects new blobs — no Pub/Sub or notifications needed.Destination:
FTP Server
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Files are pushed to any FTP server you configure.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