Slack

Install the agntdata Slack bot to let deployed agents post messages, read channel history, and route escalations into a Slack channel.

Overview

The Slack integration uses OAuth — not a BYOK API key. Once you install the agntdata Slack app, deployed agents can call Slack connector tools (post message, read channel history, reply in thread) using the bot token agntdata stores for your workspace.

Slack is not exposed through /v1/connections/slack/*. Instead, it’s wired into the MCP gateway as a first-party connector so deployed agents get typed tools out of the box.

Prerequisites

• An agntdata workspace
• A Slack workspace where you have permission to install apps

Install

1. In the agntdata dashboard, open Integrations and click Slack.
2. Click Connect Slack to start the OAuth flow.
3. Approve the requested scopes in Slack (channel read/write, DMs, commands, app mentions).
4. You’ll be redirected back to the dashboard with a confirmation banner.

Configure

Open the Slack card again on Integrations — once the install is active the dialog exposes:

• Default agent for DMs / mentions — which deployed agent handles inbound Slack messages.
• Escalation channel — Slack channel id (C0123ABC) where agent escalations are posted.
• External-user policy — whether users outside the install workspace can chat with your agents (reject / allow-listed / allow-all).

Connector tools for agents

Once installed, every deployed agent in the workspace automatically sees these MCP tools:

Tool	Description
slack_post_message	Post a message (with optional thread reply) to a Slack channel. Returns channel + ts.
slack_conversation_history	Fetch the most recent messages from a Slack channel.
slack_conversation_replies	Fetch the messages in a Slack thread.

These tools are backed by the bot token from your install — you don’t need to paste an API key into the agent.

Disconnect

Disconnecting from the Slack dialog on Integrations revokes the bot token and removes the install row from oauth_installs. The connector tools are no longer exposed to agents in that workspace.

FAQ

Why isn’t Slack listed under /v1/connections/:vendor/*? Slack uses OAuth bot tokens managed by agntdata, not a user-pasted API key. Calls to /v1/connections/slack/* return 404 with a pointer to the connector path.

Can multiple agntdata workspaces install the same Slack app? Yes — each workspace gets its own oauth_installs row keyed by the Slack team id.

Where are tokens stored? Encrypted at rest in oauth_installs.encrypted_access_token, decrypted only when dispatching a connector tool call.