Send files from an on-premise folder to any FTP server
Drop a file in a folder on your own server and DocEvent delivers it to any FTP server automatically. The Filerouter agent watches the folder, sends each completed file into your channel, and DocEvent pushes it over FTP — no scripts, no VPN, no code.
From
Filerouter (on-premise)
To
FTP
Get started for free — our basic plan is free forever.
How Filerouter (on-premise) to FTP routing works
Filerouter
Files are picked up from a watched folder on your own server by the Filerouter agent and sent into the channel.
DocEvent Channel
FTP Server
Files are pushed to any FTP server you configure.
1
File arrives via Filerouter (on-premise)
A small self-contained agent for Windows, macOS and Linux watches a local directory and sends each new file over HTTPS with an api-key. It waits for files to be fully written, filters by name or extension, and confirms every transfer — nothing is lost or sent twice.
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 Filerouter (on-premise) → FTP channel.
- Deliver ERP or accounting exports from a local output folder to partner FTP servers
- Replace scripted FTP uploads with a watched folder that just works
- Send warehouse or branch-office files to head-office FTP drop zones
- Bridge on-premise applications to FTP-based trading partners without VPNs
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Filerouter (on-premise) or FTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Filerouter
A small self-contained agent for Windows, macOS and Linux watches a local directory and sends each new file over HTTPS with an api-key. It waits for files to be fully written, filters by name or extension, and confirms every transfer — nothing is lost or sent twice.
Files are picked up from a watched folder on your own server by the Filerouter agent and sent into the channel.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
Related channel integrations
Other destinations from Filerouter (on-premise)
Other sources to FTP