Collect files from your SFTP server into SharePoint
DocEvent polls your SFTP server over SSH on a schedule, collects each new file and delivers it into a Microsoft 365 SharePoint document library. Host-key verification on the pull, no software on the SFTP server, and a full audit trail.
From
SFTP Pull
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 SFTP Pull to SharePoint routing works
Source
SFTP Pull
DocEvent connects to your SFTP server on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
SharePoint
Files are delivered into a SharePoint document library.
1
File arrives via SFTP Pull
Scheduled outbound polling of any SFTP server over SSH — nothing to install on it. Host-key verification, filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed 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 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 SFTP Pull → SharePoint channel.
- Bring partner SFTP deliveries into a Microsoft 365 library
- Give staff SharePoint access to files that arrive over SSH
- Replace a scripted SFTP-to-SharePoint copy job
- Archive an SFTP inbox where it can be searched and versioned
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP Pull or SharePoint side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SFTP Pull
Scheduled outbound polling of any SFTP server over SSH — nothing to install on it. Host-key verification, filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder.
DocEvent connects to your SFTP server on a schedule and collects new files.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
- Email → SharePoint
- AS2 → SharePoint
- Filerouter (on-premise) → SharePoint
- FTP 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