HTTP Request Node
Your workflow has what it needs, and now another system has to hear about it: post a booking to your scheduling system, send an extracted invoice to accounts, or fetch today's price list. The HTTP Request node calls an HTTP API at a fixed point in the flow and stores the response for later steps.
You'll find it under Data in the node picker.
Node or action?
This page is about the flow step: it calls the API every time the run reaches it, with the request exactly as you configure it. If you'd rather let the AI Agent decide when to call an API and fill in the details, use the HTTP Request action on the agent's Action port instead.
Options

| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| URL | Endpoint to call. Supports {{variables}} from earlier steps. Internal/private addresses are blocked. | |||
| Method | Default HTTP method. In the AI action tool the AI picks the method per call and falls back to this; a flow step uses it directly. | GET · POST · PUT · PATCH · DELETE · HEAD | POST | |
| Headers | Fixed request headers. Values support {{variables}}. | |||
| Auth | None · Bearer token · API key (header) · Basic (user:password) | none | ||
| API key header | Header name to send the API key in. Default: X-API-Key. | Auth is API key (header) | ||
| Auth secret | Bearer token / API key / "user:password" for Basic. Stored encrypted and never shown again — use Replace to change it. | Auth is Bearer token or API key (header) or Basic (user:password) | ||
| Timeout (ms) | Max wait for a response. Default 30000, max 120000. | |||
| Body | Request body (JSON or text). Supports {{variables}} from earlier steps. | Method is POST or PUT or PATCH | ||
| Output Variable | Where to store { status, ok, body, headers }. Defaults to http_response. | |||
| Accepted statuses | Responses with these statuses count as success. Any other status marks the step as an error: the run shows "Completed with errors", and a scheduled or webhook run alerts the workspace. Add 404 here if "not found" is a normal answer your flow branches on. The response is passed on either way. Default: 200-299. |
Click + Add Row on Headers for each fixed header. Method starts on POST, so the Body field is there straight away; it's shown for POST, PUT and PATCH.
Secrets are stored encrypted
The Auth secret, and the value of any credential header (Authorization, or a header named like an API key, token, secret or password), are stored encrypted. Once saved, the field reads Secret set — stored encrypted, not shown with Replace; while replacing you can Reveal what you're typing or Keep current. There's no Generate or Rotate here — the value is issued by the service you're calling. Renaming a header that holds a secret clears its value so you enter it again.
Secrets are left out of copies, exports and templates, never stored with the run's details, and masked if the API echoes them back in its response.
Variables in a JSON body
When the Body is valid JSON, Perfox fills in each {{ variable }} and takes care of escaping. A reply that contains line breaks or quotes still produces valid JSON. Wrap the placeholder in quotes, as in "note": "".
What you get back
The response is stored in your Output Variable with four parts:
| Part | Holds |
|---|---|
status | The HTTP status code, for example 200. |
ok | true for a 2xx status. |
body | The response body. JSON responses can be read field by field, for example {{ booking_response.body.booking_id }}. |
headers | The response headers. |
The output panel on the right lists these parts so you can insert them into later steps.
Accepted statuses
Accepted statuses decides which responses count as success — default 200-299. Write status codes and ranges separated by commas, e.g. 200-299, 404.
A call that comes back with any other status, or gets no response at all, doesn't stop the run: the response (with its status and any error) is still handed to the next step, so an agent or a Condition can deal with it. But the step is marked as an error, so the run shows Completed with errors in Runs, and a scheduled, webhook or other unattended run alerts your workspace. If "not found" is a normal answer your flow branches on, add 404 so those runs stay clean.
A value that doesn't parse can't be activated: Use status codes and ranges between 100 and 599, separated by commas — e.g. 200-299, 404.
Worked example: send a booking to Acme's scheduling system
Setup. At the end of her booking flow, Asha adds an HTTP Request with URL https://api.example.com/v1/bookings, Method POST, Auth Bearer token with Acme's key, and this Body:
json
{
"customer_phone": "{{ customer_phone }}",
"note": "{{ ai_response }}"
}She sets Output Variable to booking_response.
Action. Priya confirms her slot. The run reaches the HTTP Request and posts the booking.
Result. Acme's system replies with a booking id, which later steps read as {{ booking_response.body.booking_id }}.
What just happened. The call ran at exactly that point in the flow, with the request Asha configured. No model decided whether to make it.
Keep a Knowledge Base fresh from a feed
A common pattern is Schedule trigger → HTTP Request (GET a feed) → KB Index, which re-indexes an external catalog on a timetable. See KB Index.
Next steps
- KB Index: index the response into a Knowledge Base folder.
- Document Processing: extract data from a file before sending it on.
- Integrations actions: let the agent call an API itself.