DOCEVENT AGENT (ON-PREM) IN. FTP OUT. NO SCRIPTS.
Send files from a folder on your machine to any FTP server
The DocEvent Agent watches a folder on your own machine and sends each new file into a channel; DocEvent delivers it to any FTP server. Enrolled once, managed entirely from the web console — no scripts, no VPN, full audit trail.
From
DocEvent Agent (on-prem)
To
FTP
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
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
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
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 DocEvent Agent (on-prem) to FTP routing works
Source
DocEvent Agent
A DocEvent Agent running on your own machine watches a folder and sends new files into the channel.
DocEvent Channel
routes · retries · logs
Destination
FTP Server
Files are pushed to any FTP server you configure.
1
File arrives via DocEvent Agent (on-prem)
Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
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
Plain FTP, explicit FTPS or implicit FTPS, with passive-mode data connections. Username/password authentication. Configurable port and path.
Common use cases
Real workflows that teams automate with a DocEvent Agent (on-prem) → FTP channel.
- Deliver ERP or accounting exports from a local folder to partner FTP servers
- Replace scripted FTP uploads with a console-managed watched folder
- Send branch-office files to head-office FTP drop zones
- Point the agent at an output folder remotely — no local configuration
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the DocEvent Agent (on-prem) or FTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
DocEvent Agent
Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
A DocEvent Agent running on your own machine watches a folder and sends new files into the channel.Destination:
FTP Server
Plain FTP, explicit FTPS or implicit FTPS, with passive-mode data connections. 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 DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → Amazon S3
- DocEvent Agent (on-prem) → GCS
- DocEvent Agent (on-prem) → Azure Blob
- DocEvent Agent (on-prem) → SFTP
- DocEvent Agent (on-prem) → HTTP Webhook
- DocEvent Agent (on-prem) → SES Email
- DocEvent Agent (on-prem) → AS2
- DocEvent Agent (on-prem) → SharePoint
- DocEvent Agent (on-prem) → Filerouter (on-premise)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)