Send SharePoint documents to any FTP server automatically

DocEvent checks a SharePoint document library on a schedule and pushes each new file to any FTP or FTPS server. Staff keep working in Microsoft 365; the file arrives on the FTP server without anyone downloading and re-uploading it.
From
SharePoint
To
FTP
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 FTP routing works

Source

SharePoint

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

FTP Server

Files are pushed to any FTP server you configure.
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 FTP

Active and passive FTP supported. Username/password authentication. Configurable port and path.

Common use cases

Real workflows that teams automate with a SharePoint FTP channel.
  • Publish files from a SharePoint library to a partner FTP drop zone
  • Let staff deliver documents by saving them into SharePoint
  • Bridge Microsoft 365 to an FTP-only legacy system
  • Automate a manual download-from-SharePoint-then-upload-to-FTP routine
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 FTP 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:
FTP Server
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Files are pushed to any FTP server you configure.
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