Save email attachments into an on-premise folder
Give partners an email address and their attachments appear in a folder on your own server. DocEvent extracts each inbound attachment and the Filerouter agent writes it to your chosen directory — no mailbox polling, no scripts, fully audited.
From
Email
To
Filerouter (on-premise)
Get started for free — our basic plan is free forever.
How Email to Filerouter (on-premise) routing works
Email
Email attachments are captured automatically via inbound email (Amazon SES).
DocEvent Channel
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
1
File arrives via Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
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 Email → Filerouter (on-premise) channel.
- Land emailed invoices or orders in the folder your ERP already watches
- Collect attachments from suppliers into one local processing directory
- Turn an email address into a drop-box for an on-premise workflow
- Archive inbound documents on your own server the moment they arrive
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Email or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
Email attachments are captured automatically via inbound email (Amazon SES).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 destinations from Email
Other sources to Filerouter (on-premise)