Deliver SharePoint documents into a folder on your own machine

DocEvent checks a SharePoint document library on a schedule and the DocEvent Agent writes each new file into a folder on your own machine, chosen from the web console. Outbound TLS only, every file acknowledged, full audit trail.
From
SharePoint
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) routing works

Source

SharePoint

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

DocEvent Agent

Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)

The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.

Common use cases

Real workflows that teams automate with a SharePoint DocEvent Agent (on-prem) channel.
  • Land Microsoft 365 files in the directory your ERP already watches
  • Pick the delivery folder remotely from the web console
  • Feed an on-premise application from a SharePoint library
  • Move documents from the cloud to your own hardware, audited
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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