EMAIL IN. GCS OUT. NO SCRIPTS.
Save email attachments straight into Google Cloud Storage
Give partners an email address and every attachment is delivered into your Google Cloud Storage bucket automatically. DocEvent extracts each inbound attachment and writes it to the bucket and folder you choose - no mailbox polling, no scripts, fully audited.
From
Email
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 Email to GCS routing works
SourceEmail
Email attachments are captured automatically via inbound email (Amazon SES).
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
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 Email → GCS channel.
- Land emailed invoices or orders in the bucket your pipeline reads
- Give suppliers an email drop-box that archives into GCS automatically
- Feed Document AI or OCR workflows from inbound email
- Keep the original attachments in object storage you control
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Email or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
Email attachments are captured automatically via inbound email (Amazon SES).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