Get started

Send files from an on-premise folder into SharePoint

The Filerouter agent watches a folder on your own server and each new file is delivered into a Microsoft 365 SharePoint document library. The agent connects outbound over HTTPS — no inbound ports, no sync client, and every file acknowledged.
From
Filerouter (on-premise)
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 Filerouter (on-premise) to SharePoint routing works

Source

Filerouter

Files are picked up from a watched folder on your own server by the Filerouter agent and sent into the channel.
DocEvent Channel
routes · retries · logs
Destination

SharePoint

Files are delivered into a SharePoint document library.
1

File arrives via Filerouter (on-premise)

A small self-contained agent for Windows, macOS and Linux watches a local directory and sends each new file over HTTPS with an api-key. It waits for files to be fully written, filters by name or extension, and confirms every transfer — nothing is lost or sent twice.
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 Filerouter (on-premise) → SharePoint channel.
  • Publish scanned documents from an on-site scanner into Microsoft 365
  • Get output from a line-of-business application into SharePoint
  • Replace a mapped-drive or sync-client workaround with a real transfer
  • Move files off a server nobody should be logging into
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Filerouter (on-premise) or SharePoint side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Filerouter
A small self-contained agent for Windows, macOS and Linux watches a local directory and sends each new file over HTTPS with an api-key. It waits for files to be fully written, filters by name or extension, and confirms every transfer — nothing is lost or sent twice.
Files are picked up from a watched folder on your own server by the Filerouter agent and sent 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 Filerouter (on-premise)
Other sources to SharePoint
View all 112 channel integrations

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

Get started for free