Email files collected from Azure Blob Storage automatically
DocEvent polls your Azure Blob container on a schedule and emails each new file as an attachment via Amazon SES. Configurable sender, recipient and subject — turn any container folder into an automatic email feed.
From
Azure Blob Pull
To
SES Email
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
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 Azure Blob Pull to SES Email routing works
Source
Azure Blob
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.
DocEvent Channel
routes · retries · logs
Destination
Email via SES
Files are delivered as email attachments via Amazon Simple Email Service.
1
File arrives via Azure Blob Pull
Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
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 Azure Blob Pull → SES Email channel.
- Email daily reports dropped into a blob container
- Send partner documents on to a mailbox without manual downloads
- Notify a team with the file attached as soon as it lands
- Bridge Azure storage to recipients who only work by email
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Azure Blob Pull or SES Email side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Azure Blob
Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.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 Azure Blob Pull
Other sources to SES Email