Collect files from Google Cloud Storage into an on-premise folder
DocEvent polls your Google Cloud Storage bucket and delivers every new file into a folder on your own server via the Filerouter agent — outbound HTTPS only, no VPN, no scripts, fully audited.
From
GCS Blob Pull
To
Filerouter (on-premise)
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 Filerouter (on-premise) 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
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
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 Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a GCS Blob Pull → Filerouter (on-premise) channel.
- Pull GCS files down into the folder your ERP already watches
- Land cloud pipeline output on the on-premise server that needs it
- Retire scripted gsutil downloads on office servers
- Distribute files published in a central GCS bucket to branch servers
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 Filerouter (on-premise) 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:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.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
Other sources to Filerouter (on-premise)
- Amazon S3 → Filerouter (on-premise)
- HTTP Upload → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- SFTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- Azure Blob / Datalake Pull → Filerouter (on-premise)
- Azure Files Pull → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)