HTTP Request
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.
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.
| Action | What it does |
|---|---|
| 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. |
Pre-built HTTP Request workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every HTTP Request event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn HTTP Request into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
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.
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.
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 Tiny Command?
What HTTP Request triggers does Tiny Command support?
What HTTP Request actions can I run from a workflow?
Is the HTTP Request integration real-time?
Do I need to write code to use HTTP Request with Tiny Command?
How much does the HTTP Request integration cost?
More other apps people connect.
Same category as HTTP Request, ordered by how often teams pair them. Hover the carousel to pause.
Do more with HTTP Request.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
