Move files in and out of SharePoint, automatically
A Microsoft 365 document library is a channel endpoint like any other. Have DocEvent check a library on a schedule and route whatever it finds — to an FTP or SFTP server, a webhook, an inbox, an AS2 trading partner or a folder on your own machine — or send files the other way and have them filed into SharePoint as they arrive.
Get started for free — channels are free during beta.
Connect once, then build endpoints
The Microsoft connection is a first-class thing in DocEvent, not a field on a form. Create it once and every SharePoint endpoint you build afterwards simply points at it.
1
Connect Microsoft once
Create a Microsoft connection in the console and sign in with your Microsoft 365 account. That one connection is reused by every SharePoint endpoint you build — you are not pasting a client secret into a form, and there is nothing per-endpoint to rotate.
2
Pick the site, library and folder
Search the SharePoint sites that connection can reach, choose a document library from that site, and name the folder. No site URLs to look up by hand and no IDs to copy.
3
Files move on their own
A receive endpoint collects new files on your schedule; a send endpoint delivers files into the library as they arrive in the channel. Every transfer is retried on failure and recorded in the audit log.
Both directions
SharePoint is a source and a destination, so it can sit on either end of a channel — or on both, if you are copying between libraries.
Collect from
SharePoint library
DocEvent checks the folder on your schedule, takes the files that match your pattern, then deletes or archives each one.
DocEvent Channel
routes · retries · logs
Delivered to
Any destination
FTP, SFTP, a webhook, an inbox, an AS2 trading partner, a folder on your own machine — or another SharePoint library.
From any source
Any source
S3 objects, HTTPS uploads, email attachments, AS2 messages, files pulled from your FTP or SFTP server, or a watched folder on your own machine.
DocEvent Channel
routes · retries · logs
Delivered into
SharePoint library
Filed into the site, library and folder you picked, with your choice of what happens when the name already exists.
What each side actually does
Collecting from a library
- Checks the library on your schedule — from every few minutes to hourly or longer
- Filters by filename pattern, so only the files you care about are collected
- Skips files that are still being written: an optional minimum age plus a size-stability check across two polls
- Caps how many files are taken per check, so a backlog drains steadily instead of all at once
- After a file is safely in the channel, it is deleted from the library (into the site recycle bin, so nothing is lost irrecoverably) or moved to an archive folder
- Nothing is installed in your tenant and no Power Automate flow has to be maintained
Delivering into a library
- Delivers into the site, library and folder you choose
- Decide what happens when the name already exists — keep both with a numbered name, replace the file (SharePoint keeps its version history), or fail the delivery so nothing is overwritten by accident
- Large files upload in chunks, so a big document is not an all-or-nothing single request
- Failed deliveries are retried with back-off; a file that cannot be delivered is parked for reprocessing, never dropped
- Files land as normal SharePoint documents — versioned, searchable, and subject to whatever retention policy the library already has
What you can connect SharePoint to
Collect from SharePoint, deliver to…
Browse all channel integrations — any source, any destination, in any combination.