Connect with HTTP webhooks

SFTPPlus MFT can send selected events to an HTTP endpoint as soon as they occur. These webhooks connect file transfer activity to business workflows without requiring another service to poll SFTPPlus for changes.

The event handling engine can filter events by ID or group. It can send notifications for successful file transfers, authentication failures, critical errors, administrative actions, and other recorded activity.

Use the method expected by the endpoint ​

SFTPPlus can send a webhook using the HTTP GET, PUT, or POST method. Choose the method expected by the receiving endpoint. The examples below use POST, which is a common choice for sending event payloads.

Notify when a file arrives ​

An HTTP webhook can connect an incoming partner transfer to a workflow in SAP ERP, Workday, or another business application. A typical flow is:

1. A partner uploads a file to SFTPPlus using SFTP, FTPS, or HTTPS.
2. SFTPPlus stores the file and records a successful upload event.
3. The HTTP event handler sends the event metadata to the ERP endpoint.
4. The ERP system validates the notification and starts its internal import or approval workflow.

The ERP integration only needs to handle an HTTP request. SFTPPlus remains responsible for authenticating the partner, receiving the file, enforcing file access rules, and recording the transfer in its audit trail.

Example JSON payload ​

A webhook request for a successful upload can contain JSON similar to this:

{
    "events": [
        {
            "id": "40017",
            "message": "Successfully uploaded file.",
            "timestamp": {
                "iso_8601": "2026-09-03T08:30:42Z"
            },
            "account": {
                "name": "partner-a",
                "peer": {
                    "address": "203.0.113.24"
                }
            },
            "component": {
                "name": "Partner SFTP",
                "type": "ssh"
            },
            "data": {
                "path": "/incoming/orders-2026-09-03.csv",
                "total_write": 48217
            }
        }
    ]
}

The available data fields depend on the event and are listed in the events reference documentation.

Set the headers expected by the destination ​

SFTPPlus can add multiple custom headers to every webhook request. This supports API keys, routing values, tenant identifiers, trace identifiers, and other integration-specific metadata.

Set a custom Content-Type when a custom body requires a specific media type. Set a custom User-Agent for endpoint routing, allowlists, or request tracing. The User-Agent header must use this capitalization because a lowercase user-agent header is not supported.

Send XML and SOAP payloads ​

Webhook bodies can use JSON, generic XML, SOAP XML, or a custom text template. SOAP XML is useful when integrating SFTPPlus with SAP or another established system that exposes a SOAP service but does not accept JSON.

The SOAP payload includes the SFTPPlus event details in an XML envelope and uses the application/soap+xml content type. Custom headers can be added when the service requires a SOAP action, authentication value, or another integration-specific field.

Send operational notifications to collaboration tools ​

The same event handler can send notifications directly to Slack or Microsoft Teams incoming webhooks. For example, a team channel can receive a message when SFTPPlus reports a critical error or when an important file is ready for a team member to handle.

A custom payload template can include the event message, account name, file path, server identity, and other event fields accepted by the destination service. Filters keep routine activity out of the channel and send only the events that require attention.

Transfer file metadata, not the file payload ​

An HTTP event handler sends metadata about an event. It does not include the contents of an uploaded or downloaded file. Avoiding the file payload keeps webhook requests small and allows the receiving endpoint to respond quickly.

When the destination also needs the file, use an HTTP or HTTPS location to transfer the payload, or let the authorized application retrieve it through the SFTPPlus HTTP file API. The webhook can then act as the notification that tells the destination when and where to process the file.

See the HTTP webhook event handler documentation for configuration options, payload fields, response handling, retries, and redundant endpoints.