Bring SharePoint documents down to an on-premise folder

DocEvent checks a SharePoint document library on a schedule and the Filerouter agent writes each new file into a folder on your own server. The agent connects outbound over HTTPS, so no inbound ports are opened and every file is acknowledged.
From
SharePoint
To
Filerouter (on-premise)
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 Filerouter (on-premise) routing works

Source

SharePoint

DocEvent checks a SharePoint document library on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination

Filerouter

Files are delivered into a local folder on your own server by the Filerouter agent.
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 Filerouter (on-premise)

The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.

Common use cases

Real workflows that teams automate with a SharePoint Filerouter (on-premise) channel.
  • Land Microsoft 365 documents in the folder an on-site system reads
  • Feed a local print, scan or archive process from SharePoint
  • Give an application with no internet access files saved in the cloud
  • Replace a mapped drive or sync client with an audited transfer
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 Filerouter (on-premise) 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:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.
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

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

Get started for free