Email files collected from Google Cloud Storage automatically
DocEvent polls your Google Cloud Storage bucket on a schedule and emails each new file as an attachment via Amazon SES. Configurable sender, recipient and subject — turn any GCS bucket into an automatic email feed.
From
GCS Blob Pull
To
SES Email
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 SES Email 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
Email via SES
Files are delivered as email attachments via Amazon Simple Email Service.
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 SES Email
Amazon SES with configurable sender, recipient, subject, and body. Attachment included.
Common use cases
Real workflows that teams automate with a GCS Blob Pull → SES Email channel.
- Email reports to the team as soon as they land in the GCS bucket
- Forward partner files from a GCS drop bucket to a shared mailbox
- Turn a GCS prefix into an email distribution point
- Notify recipients with the actual file attached, not just an alert
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 SES Email 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:
Email via SES
Amazon SES with configurable sender, recipient, subject, and body. Attachment included.
Files are delivered as email attachments via Amazon Simple Email Service.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