Start free
OtherReal-timeUpdated September 2026
H

HTTP Request integration

HTTP Request universal API caller

HTTP Request is the universal HTTP-action connector — make arbitrary GET/POST/PUT/PATCH/DELETE calls to any HTTP endpoint with custom headers, query parameters, body, and auth. Tiny Command exposes one action, no triggers: HTTP Request (the universal HTTP caller). For workflows that need to integrate with services that don't have first-class connectors yet (or for accessing API endpoints not exposed as typed actions on existing connectors), HTTP Request is the escape hatch. Supports common auth patterns (bearer token, basic auth, API key in header/query), JSON and form bodies, and response parsing into the workflow's downstream context. For most workflows, dedicated connectors are easier; HTTP Request is the "I need to call this specific endpoint" path.

Connect HTTP Request — start free

No credit card required · Set up in under 2 minutes

0triggers
1action
≈ 2 minto set up
Freetier · no card
Actions

Do anything HTTP Request can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

ActionWhat it doesOpen action
HTTP RequestUniversal 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.
Recipes

Pre-built HTTP Request workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

H
HTTP Request → Slack alerts

AI-triage every HTTP Request event, ping the right channel only when it matters.

H
HTTP Request → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

H
HTTP Request → Notion database

Turn HTTP Request into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Each workflow step uses 1 credit. Put a filter right after the trigger: events that don't match stop there and only use credits for the steps that already ran.

Authorize once, reuse anywhere

Connect HTTP Request once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every HTTP Request field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the HTTP Request integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect HTTP Request to TinyCommand?
Open the TinyCommand workflow builder, drop in a HTTP Request node, and click Connect. Authorize HTTP Request once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.
What HTTP Request triggers does TinyCommand support?
TinyCommand focuses on outbound actions for HTTP Request today. Use TinyCommand's universal Webhook or Schedule trigger to start HTTP Request workflows, then run any HTTP Request action you need.
What HTTP Request actions can I run from a workflow?
1 HTTP Request action are available out of the box, covering other operations like "HTTP Request". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.
Is the HTTP Request integration real-time?
HTTP Request actions execute synchronously inside your workflow. TinyCommand waits for HTTP Request's API to confirm before continuing to the next step, so downstream nodes can rely on the result.
Do I need to write code to use HTTP Request with TinyCommand?
No. Every HTTP Request trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any HTTP Request API endpoint directly.
How much does the HTTP Request integration cost?
The Free plan includes 1,000 credits a month and every integration, with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats. The HTTP Request integration itself has no per-app surcharge.
Related

More other apps people connect.

Same category as HTTP Request, ordered by how often teams pair them. Hover the carousel to pause.

AWS Lambda
Other
ActionInvoke Lambda Function
Actions only2 actions
Adobe Acrobat Sign
Other
ActionCreate Signature Agreement
Actions only3 actions
Algolia
Other
ActionAdd Object to Index
Actions only5 actions
Apify
Other
ActionGet Dataset Items
Actions only4 actions
A
AppMySite
Other
ActionGet Build Status
Actions only3 actions
Bannerbear
Other
ActionGet Template
Actions only2 actions
AWS Lambda
Other
ActionInvoke Lambda Function
Actions only2 actions
Adobe Acrobat Sign
Other
ActionCreate Signature Agreement
Actions only3 actions
Algolia
Other
ActionAdd Object to Index
Actions only5 actions
Apify
Other
ActionGet Dataset Items
Actions only4 actions
A
AppMySite
Other
ActionGet Build Status
Actions only3 actions
Bannerbear
Other
ActionGet Template
Actions only2 actions

Do more with HTTP Request.

Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 457 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.

Connect HTTP Request — start free Request a demo