Get started

Send files from a folder on your own machine into SharePoint

The DocEvent Agent watches a folder on your own machine — picked from the web console — and each new file is delivered into a Microsoft 365 SharePoint document library. Outbound TLS only, every file acknowledged, full audit trail.
From
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) to SharePoint routing works

Source

DocEvent Agent

A DocEvent Agent running on your own machine watches a folder and sends new files into the channel.
DocEvent Channel
routes · retries · logs
Destination

SharePoint

Files are delivered into a SharePoint document library.
1

File arrives via DocEvent Agent (on-prem)

Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
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 DocEvent Agent (on-prem) → SharePoint channel.
  • Publish scanned or generated documents from a local folder
  • Choose the watched folder remotely from the web console
  • Get line-of-business output into Microsoft 365 automatically
  • Move files off an internal server into a governed library
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the DocEvent Agent (on-prem) or SharePoint side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
DocEvent Agent
Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
A DocEvent Agent running on your own machine watches a folder and sends new files into the channel.
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 destinations from DocEvent Agent (on-prem)
Other sources to SharePoint
View all 112 channel integrations

You focus on integration,
we'll focus on delivery.

Get started for free