> ## Documentation Index
> Fetch the complete documentation index at: https://ara-90a60a07.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Use Reason in Slack: connect the Slack app, mention @Reason to start a Session in a thread, and choose the channels a Reason listens in and when it replies.

Reason works in Slack. Mention @Reason in a channel, or message it directly, to start a Session. Reason answers in the same thread, and a reply in that thread continues the same Session.

## Connect Slack

A Workspace owner or admin connects Slack once for the whole Workspace.

1. In Reason, open [**Customize**, then **Plugins**, then **Slack**](https://reasonmachines.com/customize?tab=plugins\&plugin=slack-bot) and choose **Connect Slack**. Slack asks you to approve the Reason app for your Slack workspace.
2. In Slack, invite @Reason to a channel.
3. Mention @Reason there with a task. It starts a Session in your Workspace and answers in the thread.

You can also ask a Reason in chat to add it to Slack. It shows a card with an **Add to Slack** button.

**Settings**, under **Channels**, shows whether Slack is connected and to which Slack workspace.

> [!NOTE]
>
> The Slack app is separate from a Slack MCP connection. The app delivers Sessions to Slack. A Slack MCP connection gives Sessions the Slack tools that one account authorized. See [Connect an agent over MCP](https://ara-90a60a07.mintlify.site/docs/mcp.md).

### Your Slack account

Reason needs to know which Reason account a Slack user is, so the work runs as that person. When your Slack email matches your Reason email, nothing is needed. Otherwise Reason sends you a private link in Slack to link your account. The Slack page in Reason shows **Your Slack account** as linked or not linked.

## Threads are Sessions

* Each Slack thread is one Session. A reply in the thread continues it.
* The Session is also in the Reason app, like any other. Continue it from there, from the CLI or from the thread.
* When several Reasons answer in one thread, each has its own Session for it.

## Which Reason answers

Your Workspace has one Slack app, and it answers as each of your [Reasons](https://ara-90a60a07.mintlify.site/docs/reasons.md), by name.

* A mention or a direct message goes to the Reason whose instructions fit the message, or else to your main Reason.
* Start the message with a Reason's name to pick that Reason.
* A message nobody tagged Reason in is considered only in channels where a Reason listens.

## Channels a Reason listens in

No Reason listens in any channel until you tell it to. To have one read every new message in a channel:

1. In Slack, invite @Reason to the channel. A private channel needs this before anything else.
2. In the Reason's own chat, tell it which channel to listen in.

Adding a channel posts nothing there. Several Reasons can listen in the same channel.

A Reason's Slack settings list the channels under **Listening in**, where **Stop listening** removes one. Mentions always reach a Reason where it listens.

## When it replies

**When to reply in Slack** is a Reason's policy for messages nobody tagged it in: plain words of up to 4,000 characters, for example "Only answer questions about billing. Stay quiet otherwise." Without a policy, the Reason's instructions decide.

Set it in the Reason's Slack settings, or tell the Reason in its chat when to reply and when to stay quiet.

The Reason follows the policy; it is not a filter on the channel.

## Who can talk to it

By default a Reason talks only to your team: the people in your Reason Workspace. A shared, named Reason can also be opened to people outside your team, such as customers in shared Slack channels. Your main Reason cannot.

Ask the Reason to change who can talk to it, or set `audience` with [Update a Reason](https://ara-90a60a07.mintlify.site/api-reference/reasons/update-a-reason.md). Once a Reason is open to customers, its runs use only what was added to that Reason itself.

## Loops woken by Slack

A [Loop](https://ara-90a60a07.mintlify.site/docs/loops.md#slack-messages) can wake on Slack: on every new message in a channel, on mentions, on keywords or on emoji reactions, with an optional condition in plain words such as "a bug report or a complaint, not praise". Use one for standing work, such as triaging a support channel, and name a channel where the Reason flags what it cannot handle.

Ask a Reason in chat to set up or change a Slack Loop.

## Who can change what

| Change | Who |
| - | - |
| Connect or disconnect Slack | A Workspace owner or admin |
| The channels a Reason listens in, and when it replies | A Workspace owner or admin, or the Reason's owner or a manager of it |

Work started from Slack is billed like any Session and needs a [plan](https://ara-90a60a07.mintlify.site/docs/plans.md).

## Disconnect Slack

On the [Slack page](https://reasonmachines.com/customize?tab=plugins\&plugin=slack-bot), a Workspace owner or admin chooses **Uninstall**, then **Confirm disconnect**. New Slack messages then stop creating Sessions in the Workspace.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.