> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Connect Slack to Tess to read channels, summarize discussions, and send messages from chat and agents.

The **Slack** connector integrates Tess with your Slack workspace. Once connected, the AI can find conversations, summarize channels, and help send updates inside chats and agents.

Slack is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A Slack account in the workspace you want to use.
  * Permission to authorize the Slack app for that workspace.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**.
    You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/slack/01-connect-panel.png" alt="PRINT: (Connectors panel with Slack highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find Slack and click Connect">
    Under **Apps**, locate **Slack** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/slack/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for Slack)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **Slack** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/slack/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing Slack as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Search messages and channels** across accessible conversations
* **Summarize discussions** with decisions, owners, and follow-ups
* **Send messages** to channels or DMs the account can access
* **Support operational updates** without leaving Tess
* **Help teams keep decisions findable** after busy threads

## Example prompts

> 1. Summarize what was discussed in the product channel today and highlight decisions, pending items, and owners.
> 2. Find messages about connectors or integrations and consolidate the main feedback.
> 3. Send a message to #marketing saying the live starts in 10 minutes.
> 4. What were the last decisions in #sales about pricing?

## Best practices

* Use the exact channel name when possible (for example, #product).
* Ask for a draft before sending messages to broad channels.
* In agents, define whether Slack is for reading, summarizing, or posting updates.

## Troubleshooting

<AccordionGroup>
  <Accordion icon="circle-question" title="Workspace authorization incomplete">
    Re-run Connect and approve the Slack workspace you intend to use.
  </Accordion>

  <Accordion icon="circle-question" title="401 / connection dropped">
    Reconnect Slack in Connectors if the app was removed or tokens were revoked.
  </Accordion>

  <Accordion icon="circle-question" title="Channel or user not found">
    Confirm the connected account can see that channel or member.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>