HTTP requests against the connection's allow-listed base URL.
Connect to a REST API with an API key. Requests are limited to the base URL.
Connect
| Credential field | Required | Where it comes from |
|---|
API key (API_KEY) | No | Sent as “Authorization: Bearer <key>”. Stored encrypted; never readable again. |
| Setting | Required | What it is |
|---|
Base URL (BASE_URL) | Yes | e.g. https://api.example.com - every request stays under it |
Request timeout (ms) (TIMEOUT_MS) | No | |
| Tool | Access | What it does |
|---|
HTTP request (yekar.http.request) | Write | HTTP request against the connection's allow-listed base URL. Pass saveAs to choose the file name for a download. A binary response (images, PDFs, archives) is always saved to a file and comes back as an attachment rather than being read as text. |
Notes
- Requests are restricted to the base URL you configure - path traversal and redirects off-origin are rejected.
- Your API key is sent as “Authorization: Bearer
<key>” on every request and never appears in logs or step outputs.
- Automation steps call the “http.request” tool with a method, path, query, and body.