- Triggers deliver every Slack message to your server as a webhook.
- Sessions give each user their own scoped toolset, so the agent acts as them.
- A shared connection lets the bot speak as the workspace bot, with one install for everyone.
- Redirected auth links keep OAuth out of the channel: when an app isn’t connected, the bot DMs the user a link and resumes on approval.
- The proxy reaches the Slack Web API endpoints the toolkit doesn’t wrap as tools.
Setup
You need a Composio API key, a publicly reachable URL for your server, and Bun.No public URL? Use a Cloudflare tunnel
No public URL? Use a Cloudflare tunnel
Composio posts webhooks to your server, so it needs a public URL. In local development, run a Cloudflare tunnel to expose your local port:Use the
https://…trycloudflare.com URL it prints as your APP_URL.Install the bot
A Slack bot needs a Slack app to authenticate as and a stream of events. Composio gives you both, so you never register a webhook with Slack or hold a bot token. Theslackbot toolkit ships with Composio-managed OAuth, and you install it as one shared connection for the whole workspace.
This is install.ts, run once, built up three steps at a time:
install.ts — complete file
On the callback, open the ACL to the workspace, subscribe your webhook, and create the message triggers.
install.ts
SLACK_CONNECTION_ID the server pins into every session.
Build the bot
bot.ts starts as a bare three-line agent and grows into the server, one Composio concept at a time. Each diff below is exactly what that concept adds.
Start with a basic agent
The whole idea, before any Slack: create a session for a user, hand the Pi provider the session so it can search and execute, and run a prompt. This already acts across every app that user has connected.bot.ts — step 1: A basic agent
Start from scratch. The smallest possible agent: create a session for a user, hand the Pi provider the session so it can search and execute, run a prompt. This already works against every app that user has connected, with no Slack yet.
bot.ts
Put it in a Slack thread
Turn the one-shot agent into a handler. Each Slack thread gets its own session, reused so the agent keeps context, and the reply goes back with theSLACKBOT_SEND_MESSAGE tool. The session is keyed to the Slack user, so when Alice asks for a GitHub issue it opens as Alice, against her GitHub connection.
bot.ts — step 2: Wire it to Slack threads
Turn the one-shot agent into a handler. Each Slack thread gets its own session (reused for memory), the agent runs over the session tools, and the reply is posted with the SLACKBOT_SEND_MESSAGE tool.
bot.ts
Share one workspace connection
By default a connected account is PRIVATE: only its creator can use it. The install authorized the Slack connection as SHARED, so you pin it into every session. Now Alice’s session has her GitHub connection but the workspace’s Slack connection. It posts as the bot, and acts everywhere else as Alice.bot.ts — step 3: Share one workspace connection
Pin a single SHARED Slack connection into every session. Now the bot posts as the workspace bot, but still acts in GitHub, Gmail, and everything else as the individual user.
bot.ts
Reach the gaps with the proxy
Most Slack actions areSLACKBOT_* tools. The few that aren’t, like the typing indicator and opening a DM channel, drop down to session.proxyExecute, which calls the Slack Web API with the pinned connection’s auth so you never touch a token.
bot.ts — step 4: Reach the gaps with the proxy
Add a typing indicator and a DM-channel opener. Neither has a SLACKBOT_* tool, so they drop down to the proxy, which calls the Slack Web API with the pinned connection.
bot.ts
Redirect auth links
The payoff. When the agent reaches for an app the user hasn’t connected, the tool result carries a one-time Composio connect URL. You never want it in the channel or in the model’s context. The bot extracts it, redacts it from the tool output, DMs it to the user privately, and the run resumes the moment they approve, because the session was created withwaitForConnections.
bot.ts — step 5: Redirect auth links
The payoff. When the agent touches an app the user has not connected, the tool result carries a one-time connect URL. Redact it from the model and the channel, DM it to the user privately, and let the run resume on approval.
bot.ts
Serve the webhook
Verify each trigger’s signature withcomposio.triggers.verifyWebhook, then hand the payload to handleSlackMessage off the response path so a slow handler doesn’t get retried. That’s the whole server.
bot.ts — step 6: Serve the webhook
Verify each trigger signature and dispatch the work off the response path. This is the whole server.
bot.ts
The whole project
The two files above are the spine. The real project rounds them out with grouped auth-link DMs, per-user routing, message chunking, reaction acks, and durable storage. Here’s a slice of the actual source, with the Composio touch-points highlighted. Browse the tree, read the files:The Slack bot browser is a documentation snapshot; a public repository is not available.
Run it
Runbun install.ts once to set up the bot, start the server with bun bot.ts, then @mention the bot in any channel. It opens a session as you, finds the tool it needs, runs it against your connections, and replies in thread as the workspace bot, usually within a few seconds. Ask it to do something in an app you haven’t connected yet and it DMs you a link first, then continues once you approve.