HTTP Request step¶
step_type: http_call
Calls any HTTP endpoint with a configurable method, query string, headers, and body. The response is made available to downstream steps.
Configuration¶
| Field | Type | Required | Description |
|---|---|---|---|
method |
enum | required | HTTP method: GET, POST, PUT, PATCH, DELETE, or HEAD. Defaults to GET. |
url |
string (uri) | required | The request URL. |
query |
array | optional | Query string parameters, as key/value pairs. |
headers |
array | optional | Request headers, as key/value pairs. |
body |
object | optional | Request body. content_type is application/json or text/plain; fields is a list of key/value pairs assembled into the body, with values resolved as expressions. |
When to use it¶
- Calling a third-party API that doesn't have a dedicated Flixir step.
- Posting workflow data to an internal service, spreadsheet backend, or notification tool.
- Fetching extra data mid-workflow before a later step acts on it.
Note
body fields values support expressions, so you can reference trigger and step data directly — e.g. trigger.payload.title, or jsonpath(steps.debug_a, "$.variables[0].value") to reach into a step's output. See the Expressions guide for the full syntax.