Connect HTTP / Webhook to SFTP (key-based auth)

Use 4 documented HTTP / Webhook triggers to run 1 documented SFTP (key-based auth) actions.

4 source triggers

1 target actions

Reverse direction supported

Start Free Trial Browse HTTP / Webhook integrations

Why Connect HTTP / Webhook & SFTP (key-based auth)?

Start with a HTTP / Webhook event

Choose from 4 documented triggers, including New Requests, New Requests (Payload Only), New event when the content of the URL changes..

Run a SFTP (key-based auth) action

Send the event into one of 1 documented actions, such as Upload File.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

HTTP / Webhook

Triggers (4)

New Requests

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

polling

New Requests (Payload Only)

Get a URL and emit the HTTP body as an event on every request

polling

New event when the content of the URL changes.

Emit new event when the content of the URL changes.

polling

New Webhook Request

Emit new event when an HTTP request is received at the webhook URL. Use as a trigger to run workflows from external services (GitHub, Stripe, n8n, etc.). Configure response code, body, and which HTTP methods to accept.

webhook

Actions (7)

Send any HTTP Request

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

Send GET Request

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

Send POST Request

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

Send PUT Request

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

Return HTTP Response

Use with an HTTP trigger that uses "Return a custom response from your workflow" as its HTTP Response

Validate Webhook Auth

Require authorization for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

Verify HMAC Signature

Validate HMAC signature for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

SFTP (key-based auth)

Triggers (1)

New Remote Directory Watcher

Emit new events when files get created, changed or deleted from a remote directory. See the docs

polling

Actions (1)

Upload File

Uploads a file or string in UTF-8 format to the SFTP server. See the documentation

Integration Features

4 documented HTTP / Webhook triggers

1 documented SFTP (key-based auth) actions

Configurable field mapping

Conditional workflow steps

Execution monitoring

A supported SFTP (key-based auth) to HTTP / Webhook direction

Capability Examples

HTTP / Webhook trigger → SFTP (key-based auth) action

Catalog example

HTTP / Webhook

New Requests

SFTP (key-based auth)

Upload File

SFTP (key-based auth) trigger → HTTP / Webhook action

Reverse direction

SFTP (key-based auth)

New Remote Directory Watcher

HTTP / Webhook

Send any HTTP Request

How It Works

Connect Apps

Authenticate your HTTP / Webhook and SFTP (key-based auth) accounts

Choose a Trigger

Select a documented HTTP / Webhook event

Choose an Action

Select the documented SFTP (key-based auth) operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 4 documented HTTP / Webhook triggers.

Automated Actions

Run one of 1 documented SFTP (key-based auth) actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Reverse Integration Available

Also connect SFTP (key-based auth) to HTTP / Webhook for bidirectional automation

View Integration

All HTTP / Webhook Integrations

Explore all available HTTP / Webhook connections

View All Integrations

All SFTP (key-based auth) Integrations

Explore all available SFTP (key-based auth) connections

View All Integrations

Popular Integrations

View all integrations →

More SFTP (key-based auth) Integrations

View all SFTP (key-based auth) integrations →

Ready to Connect HTTP / Webhook & SFTP (key-based auth)?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free

Connect HTTP / Webhook to SFTP (key-based auth)

Why Connect HTTP / Webhook & SFTP (key-based auth)?

Start with a HTTP / Webhook event

Run a SFTP (key-based auth) action

Map and review the workflow

Available Triggers & Actions

HTTP / Webhook

Triggers (4)

Actions (7)

SFTP (key-based auth)

Triggers (1)

Actions (1)

Integration Features

Capability Examples

HTTP / Webhook trigger → SFTP (key-based auth) action

SFTP (key-based auth) trigger → HTTP / Webhook action

How It Works

Connect Apps

Choose a Trigger

Choose an Action

Test and Review

Frequently Asked Questions

Is the HTTP / Webhook to SFTP (key-based auth) direction supported?

Which HTTP / Webhook triggers are available?

Which SFTP (key-based auth) actions are available?

Can I also connect SFTP (key-based auth) to HTTP / Webhook?

Integration Benefits

Trigger-driven Workflows

Automated Actions

Provider Authentication

Guided Configuration

Field Mapping

Execution Review

Reverse Integration Available

All HTTP / Webhook Integrations

All SFTP (key-based auth) Integrations

Popular Integrations

More SFTP (key-based auth) Integrations

Ready to Connect HTTP / Webhook & SFTP (key-based auth)?