http(s) URL and returns the status, headers and body. It needs no connection: the caller supplies the URL and any headers.
Reliant refuses requests to private, loopback, link-local and cloud-metadata addresses, checked after DNS resolution, so a workflow cannot be pointed at your internal network or at a machine’s metadata service.
The action
http/request@1 takes:
It returns
status, headers (names lower-cased), json (the parsed body, or null) and text (the raw body), under the action node’s data: read them as nodes.<id>.data.status, nodes.<id>.data.json and so on. Responses are limited to 1 MiB.
Credentials
To authenticate, save an API-key or basic-auth connection for thehttp integration and name it with connection:. The credential is sent only to the host the request started at, so a redirect to another site does not carry it along. An API-key connection picks its header from a fixed list, because this integration does not know any particular API.
A saved generic HTTP connection is not bound to an initial destination. The workflow chooses that destination with url; any public HTTPS host can receive the selected credential. Redirect protection prevents forwarding it to a second host, but does not establish that the first host is trusted. Secret redaction also does not prevent disclosure to the remote server.
For authenticated requests, use a literal trusted origin in the workflow, or a named integration whose manifest constrains its hosts. Do not construct the origin from caller input, model output, or fetched content. If an input must be retained for compatibility, check it against an independently fixed trusted origin before any authenticated action; an allowlist supplied by that same caller is not a trust boundary. Disabling redirects alone does not fix an untrusted initial URL.
Secrets
A workflow can authenticate a request with a stored secret, such as an API key, without the value ever appearing in anything a step or a model can read. Declare the secrets at the top of the workflow, then put one in a credential slot:The two credential slots
A secret is a validation error everywhere else, and the step refuses it again when it runs: an HTTP
url, query or body, any other action input, a run command, prompts and messages, save_message, tool configs, invoke_tool, conditions, compute, while, key, items, edges and workflow outputs. A header that carries a secret cannot be Host, Content-*, Transfer-Encoding, Connection or a Proxy-* header. Only a whole {{ secrets.NAME }} is a secret reference; secrets['NAME'], secrets.NAME.upperAscii() and concatenations are refused.
credential is refused next to connection or hosted_use, and for an integration that has no api_key method, sends its key in the query string, leaves the header to each connection (http/request@1: use a header slot), or needs connection settings a key does not carry (Sentry’s organization: use a saved connection).
run steps never receive a secret: a command can print its own environment, so there is nothing to put one in that it could not echo.
What Reliant keeps
The value is fetched by the worker for one step attempt, through the control plane, and written only into the outgoing request. It is never a step input, so it is not in the run’s state, the Temporal history, the write ledger, logs, spans, node outputs, errors or the UI. Nothing is masked after the fact: the value is simply never in that text. A request that carries a secret is held to the same transport rules as one that carries a saved connection: it is sent only over HTTPS, and redirects and pagination links are followed only within the host the request started at (an integration credential also only to the integration’s own hosts). A redirect to another host fails the step instead of being followed. The remote server receives the value, and what it does with it is its own. If it echoes your request headers back (such as a debugging endpoint), the step’s recorded output shows[secret] in place of the value, but the server has still seen it. Send a secret only to the API it belongs to.
Text that reaches a step as data, such as a workflow input or the output of an earlier step, is never treated as a secret reference, even if it contains {{ secrets.NAME }}.
Access
A secret’s access list decides which workflows may use it. An org owner or admin allows a workflow withforge env secret allow TRADER_KEY --env staging --workflow trader-bot. A workflow that is not on the list fails the step with a message that names that command. The activation and trigger approval list each secret a workflow uses (name and environment), so adding one is a change the owner approves.
Loops and sub-workflows
Any number of steps may use a secret, including steps inside loops and parallel loops, with nothing to configure per step. An inlineloop or workflow body uses the root workflow’s declarations. A workflow loaded by ref is a separate workflow and declares its own secrets; the parent’s are not passed down, and its access list is checked against the child’s own name.