HPer-pair page

Connect Slack to HTTP Request in two minutes.

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

Trigger app
Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →
H
Action app
HTTP Request as the action

Workflows do something in HTTP Request, instantly.

Connect Slack to HTTP Request — start free
Both directions

Pick the way that fits your stack.

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

HSlackHTTP Request

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

13 Slack triggers wired to 1 HTTP Request actions. Most-used pairing: App Home OpenedHTTP Request.

HHTTP RequestSlack

Or fire it the other way around.

0 HTTP Request triggers wired to 45 Slack actions downstream.

  • Use any trigger in the catalog as the upstream.
See HTTP RequestSlack
Popular pairings

Common Slack → HTTP Request workflows.

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

Showing 3 of 13 combinations
How it works

Connect Slack and HTTP Request in five steps.

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

  1. 1
    Connect
    Authorize Slack and HTTP Request

    Open TinyCommand, authorize Slack and HTTP Request once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Slack trigger

    Drop the Slack → App Home Opened trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/slack.trigger-app-home-opened
  3. 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. 4
    Action
    Add the HTTP Request action

    Drop the HTTP Request → HTTP Request action below it. Map fields from the Slack payload into the HTTP Request inputs.

    http-request.request
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Slack + HTTP Request.

How long does it take to connect Slack and HTTP Request on TinyCommand?
Under two minutes. Authorize Slack and HTTP Request once each, drop the Slack trigger and HTTP Request action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Slack ↔ HTTP Request integration real-time?
Yes. Both Slack and HTTP Request 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 Slack and HTTP Request?
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 HTTP Request.
What Slack events can trigger a HTTP Request workflow?
Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.
Do I need a paid plan to use Slack with HTTP Request?
No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.
What if I want HTTP Request → Slack instead?
Build it the same way, in reverse. There's a dedicated /integrations/http-request/with/slack page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Slack.


Connect Slack to HTTP Request — start free