Collect files from S3-compatible buckets and deliver over SFTP

DocEvent polls your S3-compatible bucket — Cloudflare R2, MinIO, Backblaze B2, Wasabi or Amazon S3 — on a schedule and delivers every new file to an SFTP server over SSH. Secure bucket-to-SFTP delivery with no scripts and a full audit trail.
From
S3 Compatible (pull)
To
SFTP
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.

How S3 Compatible (pull) to SFTP 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

SFTP Server

Files are pushed securely to an SFTP server over SSH.
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 SFTP

SSH key or password authentication. Standard port 22. Configurable remote path.

Common use cases

Real workflows that teams automate with a S3 Compatible (pull) SFTP channel.
  • Forward files landing in R2, B2 or Wasabi to bank or insurer SFTP portals
  • Bridge object storage to partners that only accept secure SFTP delivery
  • Collect MinIO output on a schedule and deliver it over SSH with host-key verification
  • Automate regulated file submissions from any bucket — no notifications required
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 SFTP 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:
SFTP Server
SSH key or password authentication. Standard port 22. Configurable remote path.
Files are pushed securely to an SFTP server over SSH.
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