HActionHTTP RequestUpdated June 2026

How do I make an arbitrary HTTP request?

Short answer: Drop the "HTTP Request → HTTP Request" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 1 HTTP Request actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Method method	options	Required	HTTP method
URL url	string	Required	Full URL including protocol. Query string can be inline here or split into `query_params` below.
Headers headers	object	Optional	Key-value map of request headers. Authorization headers go here.
Query Parameters query_params	object	Optional	Optional key-value map. Appended to the URL as ?key=value (URL-encoded).
Body (JSON) body	object	Optional	JSON body for POST/PUT/PATCH. Ignored for GET/HEAD/DELETE/OPTIONS.
Timeout (ms) timeout_ms	number	Optional	Request timeout in milliseconds. Default 60000 (60s).

Sample request

{
  "method": "{{trigger.method}}",
  "url": "https://api.example.com/v1/resource",
  "headers": "{ \"Authorization\": \"Bearer xyz\", \"X-Custom\": \"value\" }",
  "query_params": "{{trigger.query_params}}",
  "body": "{ \"key\": \"value\" }"
}

Returns

{
  "ok": true,
  "body": {
    "id": "abc123",
    "name": "Example"
  },
  "status": 200,
  "headers": {
    "content-type": "application/json"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about HTTP Request.

What does the HTTP Request action do in HTTP Request?

Universal HTTP caller — GET/POST/PUT/PATCH/DELETE to any URL with custom headers, query params, body, auth. The escape hatch for services without first-class connectors or for endpoints not exposed by existing typed actions.

What inputs does HTTP Request require?

Required: Method, URL. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if HTTP Request returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does HTTP Request support batch operations?

Yes. Run HTTP Request inside a Loop node to process arrays. Tiny Command handles HTTP Request's rate limits automatically so you don't have to throttle manually.

How do I make an arbitrary HTTP request?

The fields this action accepts.

Apps that pair well as the trigger for HTTP Request.

Questions about HTTP Request.

Send http request from your workflows.