HTTP Request
Use responses from a public HTTP endpoint in your graph.
Starter · 0 SCH
Install HTTP Request, then add its HTTP Request action to a visual command or event. Choose the URL and method. Headers and a request body are optional; GET and HEAD do not send a body.
Set Save outputs as to a name such as http. Later actions can use:
| Variable | Value |
|---|---|
{store:http.ok} | true for HTTP 200–299, otherwise false. |
{store:http.status} | HTTP status code, or 0 if the request could not complete. |
{store:http.latency} | Request duration in milliseconds. |
{store:http.text} | Response text. |
{store:http.body.database.status} | A value from a JSON response, in this example database.status. |
{store:http.error} | Reason a request could not complete. |
JSON arrays use numeric paths, such as {store:http.body.services.0.name}. Up to 256 values and eight levels of nesting are exposed. Keys can contain letters, numbers, underscores, and hyphens.
Use a Condition on {store:http.ok} to handle failures. An unreachable endpoint or HTTP error does not stop the graph, so a status panel can show an unavailable state.
Request limits
Each bot can make 10 requests per minute, with 2 in progress at once. Requests time out after 5 seconds. Request bodies can be up to 16 KB; responses up to 128 KB. Responses must be uncompressed. No automatic retries are made.
URLs must use public HTTP or HTTPS on port 80 or 443. Localhost, private networks, and cloud metadata addresses are unavailable. Put authentication in headers rather than the URL. Custom headers are removed when a GET or HEAD request redirects to a different origin; other methods cannot follow such redirects.
HTTP Request uses no schedule slots. Add Timer when you want recurring checks. Endpoint providers may have their own charges and limits.