POST files from an on-premise folder to any HTTP endpoint
Turn any folder on your own server into an API feed. The Filerouter agent watches the folder and sends each new file into a DocEvent channel, which POSTs it to your HTTP or HTTPS endpoint with automatic retries.
From
Filerouter (on-premise)
To
HTTP Webhook
Get started for free — our basic plan is free forever.
How Filerouter (on-premise) to HTTP Webhook 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
HTTP Webhook
Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
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 HTTP Webhook
Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.
Common use cases
Real workflows that teams automate with a Filerouter (on-premise) → HTTP Webhook channel.
- Feed cloud processing 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 Filerouter (on-premise) or HTTP Webhook 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:
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
Related channel integrations
Other destinations from Filerouter (on-premise)
Other sources to HTTP Webhook