POST files from a folder on your machine to any HTTP endpoint
The DocEvent Agent watches a folder on your own machine and DocEvent POSTs each new file to your HTTP or HTTPS endpoint with automatic retries. Enrolled once, managed from the web console — turn any local folder into an API feed.
From
DocEvent Agent (on-prem)
To
HTTP Webhook
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 DocEvent Agent (on-prem) to HTTP Webhook routing works
DocEvent Agent
A DocEvent Agent running on your own machine watches a folder and sends new files into the channel.
DocEvent Channel
HTTP Webhook
Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
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 HTTP Webhook
Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.
Common use cases
Real workflows that teams automate with a DocEvent Agent (on-prem) → HTTP Webhook channel.
- Feed cloud pipelines from files written by on-premise software
- Send scanner, lab or instrument output folders to a REST API
- Bridge legacy applications that only write files to modern webhooks
- Upload machine-generated data from factory or branch sites to cloud services
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 HTTP Webhook 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:
HTTP Webhook
Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.
Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.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