Skip to main content
The HTTP API step makes a single HTTP request and captures the response in the workflow context. It’s the go-to step for talking to external systems that don’t have a dedicated Action integration.
HTTP API step inspector

When to use it

Inspector fields

For POST, PUT, and PATCH requests, a body editor appears for the request payload.

What lands in ctx

After the step runs, it adds to ctx under the step’s name:
Reference downstream:

Test the request

Use the Test button in the step inspector to run the request on demand — no full workflow run required. The test dialog lets you supply values for the upstream variables the request references, then executes the real request (same SSRF protection, body encoding, and response parsing as production). It shows the evaluated Request and the full Response (status, headers, body, and elapsed_ms) so you can confirm the call is shaped correctly before wiring it into the workflow.

Examples

Authenticated GET with query params

URL: https://api.example.com/contacts Headers:
Query parameters:

POST with a dynamic JSON body

Method: POST URL: https://api.example.com/tickets Body:

AI-generated request body

Limits