GCS BLOB PULL IN. GCS OUT. NO SCRIPTS.
Move files between Google Cloud Storage buckets on a schedule
DocEvent polls one Google Cloud Storage bucket on a schedule and delivers every new file into another - across projects, accounts or organisations. GCS-to-GCS transfer with filename filtering, no Pub/Sub, no scripts and a full audit trail.
From
GCS Blob 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 GCS Blob Pull to GCS 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
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
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 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 GCS Blob Pull → GCS channel.
- Copy between GCS projects or accounts without IAM cross-grants
- Collect a partner's drop bucket into your own on a schedule
- Fan production output into staging and analytics buckets
- Bucket-to-bucket movement with an audit trail, not a cron job
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 GCS 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:
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
Related channel integrations
Other destinations from GCS Blob Pull