Collect files from FTP servers into an on-premise folder
DocEvent polls a remote FTP or FTPS server and delivers every new file into a folder on your own server via the Filerouter agent — outbound HTTPS only, no VPN, no scripts, fully audited.
From
FTP Pull
To
Filerouter (on-premise)
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
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 FTP Pull to Filerouter (on-premise) routing works
FTP Pull
DocEvent connects to your FTP or FTPS server on a schedule and collects new files.
DocEvent Channel
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
1
File arrives via FTP Pull
Scheduled outbound polling of any FTP or FTPS server — nothing to install on it. Filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder. TLS certificate verification for FTPS.
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 Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a FTP Pull → Filerouter (on-premise) channel.
- Pull partner FTP files down into the folder your ERP already watches
- Retire ad-hoc download scripts on office servers with one managed channel
- Collect from a hosted FTP service into your local processing directory
- Give branch offices local copies of files published on a central FTP server
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the FTP Pull or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
FTP Pull
Scheduled outbound polling of any FTP or FTPS server — nothing to install on it. Filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder. TLS certificate verification for FTPS.
DocEvent connects to your FTP or FTPS server on a schedule and collects new files.Destination:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.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
Related channel integrations
Other destinations from FTP Pull