HTTP Request Step
The HTTP Request step makes one outbound call and stores the response.The payload
The path, or the whole URL if
base_url is not set. base_url and url are joined with a / between them.The request body. An object or array is JSON-encoded and sent with
Content-Type: application/json. A string is sent as it is: it is labelled application/json when it parses as JSON and application/x-www-form-urlencoded otherwise, so form-encoded token requests work without extra setup. An empty string sends no body. A Content-Type header you set yourself always wins. The field is data, not body.Query-string parameters.
params is accepted as a synonym; both are merged into the URL and every value is stringified.There are two places to set a timeout and the payload’s own
timeout wins. The Timeout field under Advanced Settings applies only when the payload does not carry one, so set whichever suits you — but not both, expecting the smaller to hold.Authentication
The Authorization tab writes anauth object into the payload:
A bearer token. The scheme word is prefixed automatically if the value does not already start with it.
A stored OAuth connection. The step fetches a live token for it at run time and uses it as the bearer.
When the payload also carries
security_schemes (an OpenAPI-shaped map, which the Integration step supplies), this names the scheme to use and it decides the placement. Without security_schemes it is the scheme word, defaulting to Bearer.Secrets
Never paste a credential into a payload. Store it as a secret and reference it asSECRET::<name>:: — the reference is substituted with the secret’s value when the run loads the flow, so the literal never sits in the flow configuration:
secrets object to read with JSONPath — $.secrets.… resolves to nothing.
The response
Failure and retries
Three settings under Advanced Settings are the whole of the error-handling model:Status codes the step should treat as an expected outcome. A listed code is not retried and does not end the run: the step returns a result carrying
status_code and error, alongside the response’s own status, statusText, headers and data, so a Condition step can branch on $.STEP.status_code.Only a code that arrives as an HTTP status can be listed. A request that never gets a response, such as a timeout or a connection failure, has no status and still fails the step. A code that is not listed fails the step as before.
Flattens the response into dotted keys before storing it, turning
$.STEP.data.id into the key data.id.Testing a call
The Request tab has a Send button that issues the call immediately and shows the response, and a Lookup sub-tab holding sample run data so$. paths resolve while you are testing.
Two conveniences sit above the method field: Copy as cURL and Import from cURL, which is the fastest way to get a working request in from an API’s own documentation.
Editing a flow changes its draft. Publish to make the change take effect.
HTTP Request compared with an Integration step
Use the Integration step when the service is already connected to your account — it picks the action from the integration’s own catalogue, fills in the URL and method, and handles the credential. Use HTTP Request for anything else, or when you need exact control over the request.Next Steps
Integration Step
Call a connected service instead
Map Step
Reshape the response for the next step
Variable Mapping
JSONPath reference for the payload
Flow Steps Overview
How a failure ends a run