Pull files from Google Cloud Storage onto your own machine
DocEvent polls your Google Cloud Storage bucket on a schedule and the DocEvent Agent saves each collected file into a local folder on your own machine. Enrolled once, managed entirely from the web console, fully audited.
From
GCS Blob Pull
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) 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
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a GCS Blob Pull → DocEvent Agent (on-prem) channel.
- Collect GCS drops into a local folder — no download scripts
- Land bucket files on the machine that processes them
- Manage the collection schedule and delivery folder from the console
- Keep an office server in sync with a GCS prefix — no VPN required
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
- Amazon S3 → DocEvent Agent (on-prem)
- HTTP Upload → DocEvent Agent (on-prem)
- Email → DocEvent Agent (on-prem)
- Filerouter (on-premise) → DocEvent Agent (on-prem)
- FTP Pull → DocEvent Agent (on-prem)
- SFTP Pull → DocEvent Agent (on-prem)
- S3 Compatible (pull) → DocEvent Agent (on-prem)
- Azure Blob / Datalake Pull → DocEvent Agent (on-prem)
- Azure Files Pull → DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)