GCS BLOB PULL IN. SFTP OUT. NO SCRIPTS.
Collect files from Google Cloud Storage and deliver over SFTP
DocEvent polls your Google Cloud Storage bucket on a schedule and delivers every new file to an SFTP server over SSH. Secure GCS-to-SFTP delivery with host-key verification, no Pub/Sub and a full audit trail.
From
GCS Blob Pull
To
SFTP
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
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 GCS Blob Pull to SFTP 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
SFTP Server
Files are pushed securely to an SFTP server over SSH.
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 SFTP
SSH key or password authentication. Standard port 22. Configurable remote path.
Common use cases
Real workflows that teams automate with a GCS Blob Pull → SFTP channel.
- Deliver GCS files to banks or insurers that only accept SFTP
- Automate regulated submissions straight from a GCS bucket
- Bridge Google Cloud pipelines to partners on SFTP infrastructure
- Replace scripted gsutil downloads and manual SFTP uploads
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 SFTP 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:
SFTP Server
SSH key or password authentication. Standard port 22. Configurable remote path.
Files are pushed securely to an SFTP server over SSH.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
Related channel integrations
Other destinations from GCS Blob Pull