Deliver files from any S3-compatible bucket to FTP servers
DocEvent polls any S3-compatible bucket — Cloudflare R2, MinIO, Backblaze B2, Wasabi or Amazon S3 — on a schedule, collects new files and pushes each one to your FTP server. No bucket notifications, no scripts, full audit trail.
From
S3 Compatible (pull)
To
FTP
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 FTP 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
FTP Server
Files are pushed to any FTP server you configure.
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 FTP
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Common use cases
Real workflows that teams automate with a S3 Compatible (pull) → FTP channel.
- Collect files partners drop in Cloudflare R2, Backblaze B2 or Wasabi and push them to FTP
- Bridge object storage to legacy FTP-only systems without polling scripts
- Move MinIO or private object-store output to trading partner FTP drop zones
- Work with any provider — a schedule needs no bucket notifications or event plumbing
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 FTP 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:
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