Skip to main content
The HTTP integration is the escape hatch for services that have no integration of their own. It sends a request to a public 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). Responses are limited to 1 MiB.

Credentials

To authenticate, save an API-key or basic-auth connection for the http 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.

Calling in rather than out

HTTP only makes outgoing requests. To start a run from an incoming request, use a webhook.