> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/nodes/actions/misc/http-request-action.md).
# HTTP Request Action
The HTTP Request Action node is your Swiss-Army-knife for interacting with third-party REST APIs. Use it to send HTTP requests and seamlessly integrate Helmut4 with any REST-based external system.
#### Configurable Settings
* **Async**\
Enable or disable asynchronous execution.
* **Domain Name**\
The base domain of the target API (e.g., `api.example.com`).
* **Path**\
The endpoint path to append to the domain (e.g., `/v1/users`).
* **Method**\
The HTTP verb to use: `GET`, `POST`, `PUT`, `PATCH`, or `DELETE`.
* **Headers**\
A set of request headers in `Key: Value` format.
* **Body**\
The JSON payload to include in the request (for methods that support a body).
* **Skip SSL/TLS Verification**\
Disable certificate validation for HTTPS requests—handy when the endpoint uses a self-signed certificate.
* **Timeout**\
Maximum time (in seconds) to wait for a response.
#### Response Handling
All response data—including the status code, headers, and body—is captured in the node’s response object. You can access it via wildcards:
* [{node.result.?}](/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/wildcards/result-or-return-wildcards-2/node-result.md)
* [{stream.last\_result}](/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/wildcards/result-or-return-wildcards-2/stream-last_result.md)
The object is organized into sections such as **code** (status code), **headers** (response headers) and **body** (response payload), making it easy to extract exactly what you need.
HTTP Request Action
**Example output:**
```json
{
"code":200,
"headers":{
"Transfer-Encoding":[
"chunked"
],
"null":[
"HTTP/1.1 200 OK"
],
"Version":[
"4.10.0"
],
"Vary":[
"Access-Control-Request-Headers",
"Access-Control-Request-Method",
"Origin"
],
"Date":[
"Tue, 06 May 2025 11:51:02 GMT"
],
"Content-Type":[
"application/json"
]
},
"body":{
"id":"5e21ed926d44e10001fdd2e4",
"username":"admin",
"displayname":"admin",
"email":"admin",
"lastLogin":"2025-05-06T07:04:54.585Z",
"isConnected":false,
"isFlowUser":false,
"isRenderNode":false,
"isActiveDirectoryUser":false,
"isOktaUser":false,
"role":"ADMIN",
"os":"mac",
"hostname":"MacBook-Pro.local",
"clientVersion":"4.10.0.8",
"clientSessionToken":"1952e144-c358-46e9-af22-ca4a6f596a19",
"issuer":"http://192.18.122.20",
"failedLoginAttempts":0
}
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.helmut.de/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/nodes/actions/misc/http-request-action.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.