Collect files from any S3-compatible bucket into SharePoint

DocEvent polls your S3 or S3-compatible bucket on a schedule — Cloudflare R2, MinIO, Backblaze B2, Wasabi or Amazon S3 — and delivers each collected file into a Microsoft 365 SharePoint document library. No bucket notifications or event plumbing needed.
From
S3 Compatible (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 S3 Compatible (pull) to SharePoint routing works

Source

S3 Compatible

DocEvent checks your S3 or S3-compatible bucket on a schedule and collects new files — Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.
DocEvent Channel
routes · retries · logs
Destination

SharePoint

Files are delivered into a SharePoint document library.
1

File arrives via S3 Compatible (pull)

Scheduled polling of any bucket that speaks the S3 API — Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Collects from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No bucket notifications or event plumbing needed.
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 S3 Compatible (pull) SharePoint channel.
  • Publish objects from Cloudflare R2, MinIO, B2 or Wasabi into Microsoft 365
  • Give staff SharePoint access to a self-hosted object store
  • Move files from a bucket that has no event notifications set up
  • Archive bucket output where business users can find it
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the S3 Compatible (pull) or SharePoint side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
S3 Compatible
Scheduled polling of any bucket that speaks the S3 API — Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Collects from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No bucket notifications or event plumbing needed.
DocEvent checks your S3 or S3-compatible bucket on a schedule and collects new files — Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.
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

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

Get started for free