Email files from an on-premise folder via Amazon SES

Drop a file in a local folder and it arrives as an email attachment. The Filerouter agent picks up each completed file from your on-premise server and DocEvent delivers it by email via Amazon SES — sender, recipient and subject all configurable.
From
Filerouter (on-premise)
To
SES Email
Get started for free — our basic plan is free forever.

How Filerouter (on-premise) to SES Email 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
Email via SES
Files are delivered as email attachments via Amazon Simple Email Service.
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 SES Email

Amazon SES with configurable sender, recipient, subject, and body. Attachment included.

Common use cases

Real workflows that teams automate with a Filerouter (on-premise) SES Email channel.
  • Email invoices or statements the moment your on-premise system writes them
  • Send end-of-day reports from a local reports folder to a distribution list
  • Replace manual attach-and-send workflows with a watched folder
  • Notify customers with generated documents straight from a server directory
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 SES Email 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:
Email via SES
Amazon SES with configurable sender, recipient, subject, and body. Attachment included.
Files are delivered as email attachments via Amazon Simple Email Service.
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.