Per-pair page

Claude + Slack: an AI teammate in every channel.

Build Claude-powered Slack bots — answer questions, summarize threads, draft responses, triage requests. The most natural fit for AI in a chat-first team.

Connect Anthropic and Slack See reverse direction

Trigger app

Anthropic as the trigger

Workflows fire when something happens in Anthropic.

Anthropic 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.

Anthropic → Slack

When something happens in Anthropic, do it in Slack.

0 Anthropic triggers wired to 45 Slack actions.

Slack → Anthropic

Or fire it the other way around.

13 Slack triggers wired to 21 Anthropic actions downstream.

See Slack → Anthropic →

How it works

Connect Anthropic and Slack in five steps.

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

1
Connect
Authorize Anthropic and Slack
Open Tiny Command, authorize Anthropic and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Anthropic trigger
Drop the Anthropic → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/anthropic.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 → Add Reaction action below it. Map fields from the Anthropic payload into the Slack inputs.
slack.add-reaction
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 Anthropic + Slack.

How do I build a Claude bot in Slack?

Slack App Mentioned trigger → fetch recent channel history for context → Claude Create Message → Slack Reply in Thread. The bot now answers when @-mentioned in any channel it's in.

Can Claude summarize a long Slack thread?

Yes. Use a slash command like /summarize. Workflow: Slack Slash Command trigger → Get Thread Replies → Claude summarizes → reply with the summary as an ephemeral message visible only to the requester.

How do I give Claude knowledge of internal docs (RAG)?

Index Notion/Confluence/Drive into a vector store (Pinecone, Weaviate). On each question, retrieve top-3 docs, pass to Claude as context. Cite sources in the reply so users can verify and trust.

Can Claude triage support requests posted in #help channels?

Yes. New Message in #help → Claude classifies (urgency + team) → either answer directly if Claude is confident, or @-mention the right team with a one-line summary. Massive time-saver for cross-team async.

How do I avoid Claude responding to bot messages or its own replies?

Filter the Slack trigger to skip messages with subtype = "bot_message" and skip messages where the bot user is the sender. Otherwise the bot loops on its own output forever.

Can I use Claude tool-calling to take actions from Slack?

Yes. Define tools like "create_jira_issue", "search_docs", "update_record". Claude decides which to call based on the user's message; the workflow executes the call and feeds results back. Powers agentic Slack bots without code.