Skip to main content
Fleet turns any agent into a Slack teammate your team can tag in a channel or message directly. The bot is the agent, not a relay in front of it: it runs with the agent’s own instructions, tools, and permissions. Every agent can have its own Slack app, so a single Slack workspace can run as many Slack bots as you have agents: one triaging support, one watching the on-call rotation, one digging through research.

​
Choose a setup path

LangSmith Cloud

Connect Slack once, then add a Slack app to any agent in one click.

Self-hosted

Configure a Slack OAuth provider, then create a custom Slack app per agent.
After setup, see:

​
What an agent can do in Slack

Once connected, the agent can:
  • Start a run from a mention in a channel, a direct message, or a group direct message.
  • Reply in the thread it was mentioned in.
  • Read thread and channel history for context.
  • Read file attachments on the messages it receives.
  • Pause on a sensitive tool and collect your approval in Slack.
Each agent maps to exactly one Slack app.
AI-generated content: All responses from agents in Slack are generated by AI and may contain errors or inaccuracies. Always verify important information.
The Slack integration with Fleet does not have any direct pricing. However, agent runs and traces are billed through the LangSmith platform according to your organization’s plan.For current pricing information, see the LangSmith pricing page.

​
Set up Slack on LangSmith Cloud

On LangSmith Cloud, Fleet creates and installs each agent’s Slack app for you. Connect Slack once, then add a Slack app to any agent in one click.

​
Prerequisites

  • An existing agent in Fleet. See Quickstart to create one.
  • A Slack workspace where you can install apps.

​
Step 1. Connect the Fleet Slack manager

The Fleet Slack app acts as a manager for your workspace. A single connection grants two things:
  • Slack tool access: The bot scopes an agent needs to post messages, read channel and thread history, and send direct messages.
  • App management: The scopes that let Fleet create a dedicated Slack app for an agent and install it in your workspace on your behalf, which is what makes one-click deploy possible.
To connect, open the Integrations page in Fleet, search for Slack, and click Connect on the Slack card. Fleet also runs this connection inline the first time you add a Slack app to an agent, so you can skip ahead to Step 2 and authorize when prompted.
The first time someone in your workspace connects, Slack may route the request to a Slack workspace admin. When the admin reviews it, they can either:
  • Allow Fleet to install apps: Anyone in the workspace can then create a Slack agent from Fleet without another approval.
  • Require approval for each app: Every Slack agent that Fleet creates needs a separate admin approval before it installs.
If your workspace requires per-app approval, follow Add an app that needs admin approval.

​
Step 2. Add a Slack app to an agent

1

Add Slack to the agent

In Fleet, select your agent and open its configuration sidebar. Expand the Channels drawer and select Slack. Click Add to Slack. If you have not connected Slack yet, Fleet runs the manager authorization first.(Optional) Expand Advanced and enable Allow bot triggers to let messages from other Slack bots start a run.
2

Confirm the install

Fleet creates a Slack app named after your agent, using its description and icon, and installs it in your workspace. The bot then sends you a direct message with tips for inviting it to channels and mentioning it.To confirm the app is connected, expand the Channels drawer in the agent’s configuration sidebar. A live Slack channel shows an Active status.

​
Add an app that needs admin approval

If your Slack workspace requires an admin to approve each app, Fleet saves the new app as a draft instead of installing it. Completing setup takes two rounds:
  1. Click Finish setup on the pending Slack row. Slack opens a window where you click Request to send the app to your workspace admin.
  2. After the admin approves it, return to Fleet and click Finish setup again. Fleet installs the app and activates the channel.

​
Set up Slack on Self-hosted

Self-hosted deployments do not use the Fleet Slack manager. Instead, configure a Slack OAuth provider once for the instance, then create a custom Slack app for each agent from a manifest that Fleet generates.

​
Step 1. Set up the Slack OAuth provider

Every self-hosted instance needs this one-time setup before agents can use Slack. It enables Slack tools for your agents and turns on the Slack channel, which is what lets you add custom apps in Step 2.
1

Configure Helm

Choose a provider ID, for example slack-oauth-provider. Add it to your langsmith_config.yaml, along with the organization that holds your OAuth providers, and deploy:
Confirm the Fleet pods restart. The provider ID is only a name at this point. The remaining steps create the provider it refers to.
2

Create a Slack app for the provider

Go to api.slack.com/apps and click Create New App.
3

Add bot scopes

In OAuth & Permissions, add the following bot token scopes:
  • channels:history
  • channels:read
  • chat:write
  • files:write
  • groups:history
  • groups:read
  • im:history
  • im:read
  • im:write
  • mpim:history
  • mpim:read
  • team:read
  • users:read
  • users:read.email
4

Register the provider in LangSmith

Copy the Client ID and Client Secret from Basic Information in your Slack app. In LangSmith, go to Settings > OAuth Providers and add a provider:
  • Provider ID: The ID you set as slackOAuthProvider.
  • Client ID: From the Slack app.
  • Client Secret: From the Slack app.
  • Authorization URL: https://slack.com/oauth/v2/authorize
  • Token URL: https://slack.com/api/oauth.v2.access
Register it in the organization you set as providerOrgId. Fleet resolves the provider from that organization, so a provider registered elsewhere fails with an unknown provider error.
5

Add the redirect URI to Slack

In the Slack app, go to OAuth & Permissions > Redirect URLs and add the following, replacing <hostname> with your LangSmith hostname and <provider-id> with your provider ID:
Until slackOAuthProvider is set, Fleet does not register the Slack trigger, Add Slack App stays disabled, and the Slack channel does not appear on agents.
Each custom Slack app in Step 2 gets its own OAuth provider, which the wizard registers from the credentials you paste. That is why Step 2 asks for a separate client ID, client secret, and signing secret.

​
Step 2. Create a custom Slack app

Start this flow from the agent you want the bot to run, so Fleet links the app for you when you finish.
1

Open the Slack setup dialog

Select your agent and open its configuration sidebar. Expand the Channels drawer and select Slack.You can also start from the Integrations page: select Slack & Teams in the left navigation, then in the Slack Apps section click Add Slack App.
2

Create the app in Slack

  1. Enter a name for the bot.
  2. Click Create Slack App. Fleet opens the Slack API site with a prefilled app manifest.
  3. Choose the workspace where you want to install the bot.
Do not create the Slack app outside this flow. The generated manifest sets the event subscription URL, interactivity URL, OAuth redirect URL, and scopes that Fleet needs. An app created by hand does not receive events.
3

Enter your app credentials

Back in Fleet, click Continue To Credentials and copy the following values from your new Slack app:
  • App ID: From Basic Information.
  • Client ID: From Basic Information > App Credentials.
  • Client secret: From Basic Information > App Credentials. Click Show in Slack and copy the whole value.
  • Signing secret: From Basic Information > App Credentials. Click Show in Slack and copy the whole value.
(Optional) Enable Allow bot triggers to let messages from other Slack bots start a run.Click Save Credentials.
4

Connect OAuth

  1. Click Connect OAuth. Slack opens an authorization window.
  2. Click Allow to install the app in your workspace.
Slack apps that need admin approval: If Slack shows Request instead of Allow, your workspace requires admin approval:
  1. In the Slack window, click Request to send the install request to your admin. This is what actually notifies the admin.
  2. Back in Fleet, click Save & Request Approval. Despite its name, this button only saves the app as a draft so you can resume once the admin approves.
See Finish a draft Slack app.
5

Finish setup

Click Finish. If you started from an agent, Fleet links the app to that agent. If you started from the Integrations page, choose an agent from the dropdown, or click Finish Without Agent to link one later.

​
Finish a draft Slack app

Clicking Save & Request Approval saves the app as a draft, so you keep your progress while a Slack admin reviews the install request. The draft appears under Pending Slack admin approval in the Slack Apps section. After your admin approves the app:
  1. On the Integrations page, select Slack & Teams in the left navigation to open the Slack Apps section.
  2. Click Resume Setup on the draft.
  3. Re-enter the Client secret and Signing secret. Fleet does not store secrets on a draft, so copy them from Slack again.
  4. Click Save Credentials, then Connect OAuth, then Allow in Slack.
  5. Select the agent to link the app to, then click Finish.
Each agent can have only one Slack app, and each Slack app can be linked to only one agent.

​
Use your agent in Slack

Once the app is installed, invite the agent to a channel, tag it to start a run, and respond to approval requests without leaving Slack.

​
Invite the agent to a channel

  1. In Slack, go to the channel where you want to use the agent.
  2. Type /invite @YourAgentName to invite it.
  3. Mention the agent with @YourAgentName to start a run. The agent replies in a thread.
You can also send the bot a direct message or add it to a group direct message.

​
Approve or deny actions in Slack

When an agent pauses on a tool that requires approval, it raises the request directly in Slack. The message names the tool and the action, with Approve and Deny buttons, so you can respond without leaving Slack. For more information, see Human-in-the-loop.

​
Error messages in Slack

If an agent encounters an error during a run, it replies in the Slack thread instead of going silent. For some error types, such as authentication errors, the reply includes more detail so you can resolve the issue.

​
Add Slack tools

Slack tools let your agent send messages, reply in threads, read history, and send direct messages. They work regardless of how the agent was triggered, whether through Slack, the Fleet UI, a schedule, or a webhook. For example, you could start a long-running research task in the Fleet chat UI and instruct the agent to send you a Slack message when it is done. To add Slack tools:
  1. Open your agent, then in the sidebar expand the Connections drawer.
  2. Click Add connection and add Slack if it is not already connected.
  3. Add the Slack tools you need:
    • Send Channel Message: Post a message to a channel.
    • Reply to Message: Reply in a thread.
    • Write Private Message: Send a direct message.
    • Read Channel History: Read recent channel messages.
    • Read Thread Messages: Read replies in a thread.
  4. If prompted, authorize the Slack connection.
You can also ask your agent to add these tools itself. In the agent chat, try: “Add the Slack tools so you can respond to messages.”
Set each tool to Auto to run it without approval, or Ask to require approval before it runs. For more information, see Human-in-the-loop.

​
Troubleshooting

​
Agent does not respond

If your agent is not responding, try the following:
  • Check the thread in the Fleet UI for errors.
  • Verify the agent was invited to the channel.
  • Confirm the Slack channel is not paused in the Channels drawer.
  • Delete the Slack app in the Channels drawer, then set it up again.

​
Not allowed to tag the bot

If you receive a private message saying you are not allowed to tag the bot, your Slack ID is not authorized for that agent. The agent’s owner needs to share the agent with you, either by sharing run access with the whole LangSmith workspace or with you individually.

​
Slack app stays pending approval

A Slack row that stays in the pending state is waiting on a Slack admin. Ask an admin to approve the app in Slack, then click Finish setup again. See Add an app that needs admin approval.

​
Add Slack App is disabled

On Self-hosted, the Add Slack App button in the Slack Apps section is disabled until fleet.oauth.slackOAuthProvider is set. See Set up the Slack OAuth provider.

​
Next steps

Add more tools

Connect additional services to your agent

Add more channels

Set up email, schedule, or webhook channels

Use templates

Start from a prebuilt agent template
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.
Edit this page on GitHub or file an issue.