HTTP Request

Send HTTP requests to external APIs or services with configurable methods, headers, and parameters.

The HTTP Request action allows a workflow to send HTTP requests to external APIs or services. This action supports configurable request methods, headers, query parameters, and advanced execution options.

When to use

Use the HTTP Request action to:

  • Trigger external webhooks
  • Fetch data from third-party APIs
  • Send data to external systems
  • Integrate workflows with custom or internal services

Configuration

HTTP Request Action Configuration

Method

Select the HTTP method to use for the request.

  • Supported values include GET, POST, PUT, PATCH, and DELETE.

URL

Enter the target endpoint URL to which the request will be sent.

Example:

https://example.com/api/webhook

Query Parameters

Add key–value pairs to be appended to the request URL as query parameters. Click Add parameter to include additional parameters. Each parameter consists of:

  • Key
  • Value

Example:

?limit=10&offset=10

Headers

Specify HTTP headers to be sent with the request.

  • Commonly used headers include:
    • Content-Type
    • Authorization
  • Click Add header to include multiple headers.

Example:

Content-Type: application/json

Request Body

Configure the request payload.

  • Body Type
    • None: No request body is sent.
    • (Other body types may be available depending on workflow capabilities.)

Use this section when sending data via POST, PUT, or PATCH requests.


Advanced Options

Timeout (ms)

Define the maximum time (in milliseconds) the workflow should wait for a response before timing out.

Default:

30000 ms

Follow Redirects

When enabled, the request automatically follows HTTP redirects (3xx responses).

Fail on Error Status

When enabled, the workflow execution fails if the response status code is:

  • 4xx (Client errors)
  • 5xx (Server errors)

This is useful for enforcing strict error handling in workflows.


Execution Flow

  • The HTTP Request action runs when triggered by the preceding workflow step.
  • Response data can be used by subsequent actions in the workflow.
  • If the request fails and Fail on Error Status is enabled, the workflow execution stops.