HActionHTTP RequestUpdated September 2026

How do I make an arbitrary HTTP request?

Short answer: You can http request in HTTP Request by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the HTTP Request HTTP Request action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

HTTP Request in HTTP Request — start free All 1 HTTP Request actions

HTTP Request in HTTP Request — start free

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.

Triggered by

Apps that pair well as the trigger for HTTP Request.

Any of these apps can fire this action as part of a workflow.

Google Sheets → HTTP Request

2 Google Sheets triggers

HubSpot → HTTP Request

18 HubSpot triggers

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 run history shows the failed step with its input and the error message HTTP Request returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does HTTP Request support batch operations?

Run HTTP Request inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within HTTP Request's rate limits.

HTTP Request in HTTP Request — start free