Get started
SFTP / FTPS SERVER IN. HTTP WEBHOOK OUT. NO SCRIPTS.

Turn SFTP or FTPS uploads into HTTP webhooks

DocEvent hosts an SFTP, SCP and FTPS server that senders upload to, and POSTs every completed upload to your HTTP webhook. SFTP-to-webhook with per-sender logins, retries and a full audit trail - no server to run, no polling.
From
SFTP / FTPS Server
To
HTTP Webhook
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
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
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
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 SFTP / FTPS Server to HTTP Webhook routing works

Source

SFTP / FTPS Server

DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
DocEvent Channel
routes · retries · logs
Destination

HTTP Webhook

Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
1

File arrives via SFTP / FTPS Server

A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
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 SFTP / FTPS Server → HTTP Webhook channel.
  • Give an SFTP-only partner a drop point that POSTs into your API
  • Trigger a web application or serverless function on every upload
  • Modernise an integration without asking the sender to change tools
  • Retried, deduplicated and audited - no polling on your side
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP / FTPS Server or HTTP Webhook side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters 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 SFTP / FTPS Server
Other sources to HTTP Webhook
View all 154 channel integrations

You focus on integration,
we'll focus on delivery.

Get started for free