Save email attachments straight into SharePoint
Give partners an email address and every attachment they send is filed into a Microsoft 365 SharePoint document library. DocEvent extracts each attachment from the inbound email and delivers it to the site, library and folder you choose.
From
Email
To
SharePoint
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 Email to SharePoint routing works
SourceEmail
Email attachments are captured automatically via inbound email (Amazon SES).
DocEvent Channel
routes · retries · logs
Destination
SharePoint
Files are delivered into a SharePoint document library.
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 SharePoint
Delivery into a Microsoft 365 SharePoint document library through the Microsoft Graph API, using a reusable Microsoft connection rather than a secret pasted onto the endpoint. Pick the site, library and destination folder, and decide what happens when the name already exists — keep both, replace it (SharePoint keeps the version history), or fail the delivery. Large files are uploaded in chunks.
Common use cases
Real workflows that teams automate with a Email → SharePoint channel.
- File supplier invoices from email into a Microsoft 365 library
- Collect signed documents emailed by customers into one site
- Turn an email address into a SharePoint drop box
- Stop staff manually saving attachments out of Outlook
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 SharePoint 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:
SharePoint
Delivery into a Microsoft 365 SharePoint document library through the Microsoft Graph API, using a reusable Microsoft connection rather than a secret pasted onto the endpoint. Pick the site, library and destination folder, and decide what happens when the name already exists — keep both, replace it (SharePoint keeps the version history), or fail the delivery. Large files are uploaded in chunks.
Files are delivered into a SharePoint document library.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 SharePoint
- Amazon S3 → SharePoint
- HTTP Upload → SharePoint
- AS2 → SharePoint
- Filerouter (on-premise) → SharePoint
- FTP Pull → SharePoint
- SFTP Pull → SharePoint
- S3 Compatible (pull) → SharePoint
- GCS Blob Pull → SharePoint
- Azure Blob Pull → SharePoint
- Azure Data Lake Pull → SharePoint
- Azure Files Pull → SharePoint
- SharePoint → SharePoint
- DocEvent Agent (on-prem) → SharePoint