SFTP PULL IN. FILEROUTER (ON-PREMISE) OUT. NO SCRIPTS.
Collect files from SFTP servers into an on-premise folder
DocEvent polls a remote SFTP server over SSH and delivers every new file into a folder on your own server via the Filerouter agent — outbound HTTPS only, no VPN, no download scripts, fully audited.
From
SFTP Pull
To
Filerouter (on-premise)
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 SFTP Pull to Filerouter (on-premise) routing works
Source
SFTP Pull
DocEvent connects to your SFTP server on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
1
File arrives via SFTP Pull
Scheduled outbound polling of any SFTP server over SSH — nothing to install on it. Host-key verification, filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder.
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 SFTP Pull → Filerouter (on-premise) channel.
- Pull bank or partner SFTP deliveries into the folder your ERP watches
- Retire scripted SFTP downloads on office servers
- Collect from hosted SFTP services into a local processing directory
- Distribute files from a central SFTP server to branch-office machines
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP Pull or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SFTP Pull
Scheduled outbound polling of any SFTP server over SSH — nothing to install on it. Host-key verification, filename pattern filtering, completed-file detection, then each collected file is deleted or moved to a processed folder.
DocEvent connects to your SFTP 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 sources to Filerouter (on-premise)
- Amazon S3 → Filerouter (on-premise)
- SFTP / FTPS Server → Filerouter (on-premise)
- HTTP Upload → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- AS2 → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- GCS Blob Pull → Filerouter (on-premise)
- Azure Blob Pull → Filerouter (on-premise)
- Azure Files Pull → Filerouter (on-premise)
- SharePoint → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)