Skip to main content
The HTTP action allows you to call external APIs, webhooks, and web services from your workflows. Use it to integrate with third-party services, fetch remote data, or trigger external processes.

http

Makes HTTP requests to external APIs and returns the response.

URL

The full URL to send the request to. Supports template variables. Example values:
  • https://api.example.com/users
  • https://api.example.com/users/{{ param "user_id" }}

HTTP Method

The HTTP method to use for the request. Supported methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS

Headers

HTTP headers to include with the request as key-value pairs. Common headers include Authorization, Content-Type, and Accept.

Body

The request body data. Typically used with POST, PUT, and PATCH requests. The body is automatically serialized to JSON when Content-Type is application/json.

Response Path

A JSONPath expression to extract a specific field from the response. When set, only the extracted value is returned instead of the full response. Example: access_token extracts just the token from an OAuth response.

Expected Response Code

The expected HTTP status code. If the actual response code differs, the action fails and routes to the fail step. Example: "201" for expecting a created response.

Fail If Response Empty

Whether to treat an empty response body as a failure.

Examples

GET Request

Fetch data from an external API:

POST Request

Create a resource on an external service:

Extract Field from Response

Get just the access token from an OAuth token endpoint:

Webhook Call

Trigger an external webhook with workflow data:

Chaining API Calls

Use the result of one HTTP call in another:

Next Steps

Secrets Management

Securely store API keys and tokens for your HTTP requests.

Authentication

Secure your own APIs with JWT and authentication actions.

Data Operations

Store and retrieve data from databases.

Actions Overview

Learn the fundamentals of actions in ServFlow.