Email documents saved to a SharePoint library
DocEvent checks a SharePoint document library on a schedule and sends each new file as an email attachment via Amazon SES, with a configurable sender, recipients, subject and body. Save the document in Microsoft 365 and it is emailed for you.
From
SharePoint
To
SES Email
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
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 SharePoint to SES Email routing works
Source
SharePoint
DocEvent checks a SharePoint document library on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
Email via SES
Files are delivered as email attachments via Amazon Simple Email Service.
1
File arrives via SharePoint
Scheduled polling of a Microsoft 365 SharePoint document library through the Microsoft Graph API. Connect your Microsoft account once from the console — the connection is reusable across endpoints and no secret is stored on the endpoint itself — then choose the site, library and folder. Filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
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 SharePoint → SES Email channel.
- Send new SharePoint files to a distribution list automatically
- Notify a partner by email whenever a document is published
- Distribute reports from Microsoft 365 without a mail merge
- Give an email-only recipient access to a SharePoint workflow
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SharePoint or SES Email side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SharePoint
Scheduled polling of a Microsoft 365 SharePoint document library through the Microsoft Graph API. Connect your Microsoft account once from the console — the connection is reusable across endpoints and no secret is stored on the endpoint itself — then choose the site, library and folder. Filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
DocEvent checks a SharePoint document library on a schedule and collects new files.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 sources to SES Email
- Amazon S3 → SES Email
- HTTP Upload → SES Email
- Email → SES Email
- AS2 → SES Email
- Filerouter (on-premise) → SES Email
- FTP Pull → SES Email
- SFTP Pull → SES Email
- S3 Compatible (pull) → SES Email
- GCS Blob Pull → SES Email
- Azure Blob Pull → SES Email
- Azure Data Lake Pull → SES Email
- Azure Files Pull → SES Email
- DocEvent Agent (on-prem) → SES Email