HPer-pair page

Connect HTTP Request to Slack in two minutes.

Real-time triggers from HTTP Request, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect HTTP Request and Slack See reverse direction

Trigger app

HTTP Request as the trigger

Workflows fire when something happens in HTTP Request.

HTTP Request has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

HHTTP Request → Slack

When something happens in HTTP Request, do it in Slack.

0 HTTP Request triggers wired to 45 Slack actions.

HSlack → HTTP Request

Or fire it the other way around.

13 Slack triggers wired to 1 HTTP Request actions downstream.

See Slack → HTTP Request →

Popular pairings

Common HTTP Request → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 0 of 0 combinations

How it works

Connect HTTP Request and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize HTTP Request and Slack
Open Tiny Command, authorize HTTP Request and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a HTTP Request trigger
Drop the HTTP Request → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/http-request.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the HTTP Request payload into the Slack inputs.
slack.api-request
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about HTTP Request + Slack.

How long does it take to connect HTTP Request and Slack on Tiny Command?

Under two minutes. Authorize HTTP Request and Slack once each, drop the HTTP Request trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the HTTP Request ↔ Slack integration real-time?

Yes. Both HTTP Request and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between HTTP Request and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What HTTP Request events can trigger a Slack workflow?

Use Tiny Command's universal Webhook trigger to receive HTTP Request events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use HTTP Request with Slack?

No. There's a free tier that covers most HTTP Request+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → HTTP Request instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/http-request page with the reverse-direction triggers and actions.

Other apps that pair well with HTTP Request.

H+

HTTP Request + Gmail

H+

HTTP Request + Google Sheets

Spreadsheets & Databases

H+

HTTP Request + HubSpot

CRM & Sales

H+

HTTP Request + Stripe

Payments

H+

HTTP Request + Notion

Productivity

H+

HTTP Request + Airtable