Pull files from FTP servers onto your own machine

DocEvent polls your FTP or FTPS server on a schedule and the DocEvent Agent saves each collected file into a local folder on your own machine. Enroll the agent once, configure everything from the web console, and get a full audit trail.
From
FTP Pull
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) routing works

FTP Pull
DocEvent connects to your FTP or FTPS server on a schedule and collects new files.
DocEvent Channel
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)

The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.

Common use cases

Real workflows that teams automate with a FTP Pull DocEvent Agent (on-prem) channel.
  • Collect partner FTP files into a local folder without writing download scripts
  • Land FTP-published files on the machine that processes them
  • Manage the collection schedule and delivery folder centrally from the console
  • Keep an office server in sync with an FTP drop zone — no VPN required
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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

You focus on integration,
we'll focus on delivery.

Get started for free