Collect files from your FTP server and send them as AS2
DocEvent polls your FTP or FTPS server on a schedule, collects each new file, then signs, encrypts and transmits it to your trading partner over AS2 with the MDN receipt tracked. Nothing to install on the FTP server, and no AS2 software to run.
From
FTP Pull
To
AS2
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How FTP Pull to AS2 routing works
Source
FTP Pull
DocEvent connects to your FTP or FTPS server on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
AS2
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.
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 AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Common use cases
Real workflows that teams automate with a FTP Pull → AS2 channel.
- Pick up EDI from an existing FTP outbox and transmit it over AS2
- Add AS2 to a partner relationship that only speaks FTP internally
- Schedule outbound trading-partner transmissions off an FTP drop zone
- Modernise an FTP-based EDI process without touching the FTP server
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 AS2 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:
AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.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