Skip to content
Per-pair page

Connect Slack to OpenRouter in two minutes.

Real-time triggers from Slack, ready-made actions in OpenRouter. 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 →
Action app
OpenRouter as the action

Workflows do something in OpenRouter, instantly.

Both directions

Pick the way that fits your stack.

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

SlackOpenRouter

When something happens in Slack, do it in OpenRouter.

13 Slack triggers wired to 3 OpenRouter actions. Most-used pairing: App Home OpenedOpenRouter Chat Completion.

OpenRouterSlack

Or fire it the other way around.

0 OpenRouter triggers wired to 45 Slack actions downstream.

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

Common Slack → OpenRouter workflows.

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

Showing 9 of 39 combinations
When app home opened in Slack, openrouter chat completion in OpenRouter.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, get openrouter credits in OpenRouter.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, list openrouter models in OpenRouter.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app mentioned in Slack, openrouter chat completion in OpenRouter.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, get openrouter credits in OpenRouter.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, list openrouter models in OpenRouter.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When new channel in Slack, openrouter chat completion in OpenRouter.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

When new channel in Slack, get openrouter credits in OpenRouter.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

When new channel in Slack, list openrouter models in OpenRouter.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

How it works

Connect Slack and OpenRouter in five steps.

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

  1. 1
    Connect
    Authorize Slack and OpenRouter

    Open Tiny Command, authorize Slack and OpenRouter 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. Tiny Command 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 OpenRouter action

    Drop the OpenRouter → OpenRouter Chat Completion action below it. Map fields from the Slack payload into the OpenRouter inputs.

    openrouter.chat-completion
  5. 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 Slack + OpenRouter.

How long does it take to connect Slack and OpenRouter on Tiny Command?
Under two minutes. Authorize Slack and OpenRouter once each, drop the Slack trigger and OpenRouter action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Slack ↔ OpenRouter integration real-time?
Yes. Both Slack and OpenRouter 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 OpenRouter?
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 OpenRouter.
What Slack events can trigger a OpenRouter 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 OpenRouter?
No. There's a free tier that covers most Slack+OpenRouter use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want OpenRouter → Slack instead?
Build it the same way, in reverse. There's a dedicated /integrations/openrouter/with/slack page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Slack.


Wire Slack to OpenRouter in 2 minutes.

Free tier available. No credit card. No onboarding call.