> For the complete documentation index, see [llms.txt](https://notara-1.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara-1.gitbook.io/notara-docs/getting-started/slack-setup.md).

# Connecting Slack

MCP is the main way to connect an agent to Notara. Slack is an optional interface for teams that want conversations and approvals inside their Slack workspace.

Your team creates and owns a private Slack app. You can choose its name and icon. Notara hosts the connection and runs the agent; your team manages the Slack app, its permissions and its credentials. Public distribution is not required.

## Before you start

You need administrator access to your Notara workspace and permission to create and install an app in the Slack workspace you want to use. If your Slack organization requires app approval, ask its administrator to approve the installation.

Agent conversations also require a model connection and the applicable workspace access. Connecting Slack does not supply a customer model key or change billing.

## 1. Create and install the app

1. Open **Connections** in Notara.
2. Under **Optional Slack connection**, select **Connect your own Slack app**.
3. Enter the app name, then choose **Create app in Slack**. The template supplies permissions, message events and callback URLs for this Notara workspace.
4. Select your Slack workspace and create the app.
5. In Slack's app settings, open **OAuth & Permissions** and install the app to that workspace.

If you already created an app, use **Copy manifest** in Notara. Paste it into that app's **App Manifest** settings and save, then install or reinstall it to apply the permissions. Customize the app's icon and name in Slack.

## 2. Validate its credentials

In the same Slack app, copy:

* **Bot User OAuth Token**, beginning with `xoxb-`, from **OAuth & Permissions**.
* **Signing Secret** from **Basic Information → App Credentials**.

Enter both values in Notara and select **Validate credentials**. Notara checks the token, required permissions, app identity and Slack workspace. It encrypts the credentials and clears the form fields. Saved secrets are not displayed again.

This prepares the connection without replacing an existing installation. Pending setup expires after 24 hours.

## 3. Verify and activate

1. In Notara, select **Open event settings**.
2. In Slack's **Event Subscriptions**, verify the **Events Request URL** shown by Notara. If needed, paste it into the Request URL field and retry verification. Save the settings.
3. Confirm the app manifest also configured **Interactivity & Shortcuts** with the **Interactivity Request URL** shown in Notara.
4. Return to Notara and select **Check verification**.
5. When the signed request is verified, select **Activate connection**.

Activation replaces this Notara workspace's Slack connection. Knowledge, workflows, memberships and MCP connections stay in place. Existing installations in other Notara workspaces are unaffected.

## Add the bot to channels

Invite your new bot to each channel where you want to use it. In Slack, open the channel's integrations and add the app, or use `/invite @YourBotName`. A replacement bot must be invited even if the previous bot was already a member.

Mention the bot in a channel or send it a direct message to test it. Check the model connection if the agent reports that no model is configured. The **Check connection** button in Notara verifies the bot token; a real message also checks event delivery and agent configuration.

## Manage, rotate or disconnect

Use **Connections → Manage Slack app** to replace credentials or switch to another app in the same Slack workspace. Repeat validation, request verification and activation. Coordinate signing-secret changes with this setup because Slack starts signing requests with the regenerated secret.

**Disconnect** revokes the installed bot token and removes the stored connection credentials. It preserves Notara data and the linked Slack workspace so you can reconnect to that same workspace. It also pauses any Notara platform notification route using that connection.

Revoking the bot token deactivates the bot and removes its channel memberships. To remove the app's listing completely, use Slack's **Manage apps** controls. Reinstalling requires a new token and inviting the bot to its channels again.

## Troubleshooting

* **Missing permissions:** paste the current manifest into Slack, reinstall the app, then validate the token again.
* **Wrong workspace:** use an app installed in the Slack workspace already linked to this Notara workspace. Disconnecting does not change that binding. Contact support if the binding needs to move.
* **Request verification fails:** check that the signing secret comes from the same app as the bot token, validate it in Notara, then verify the exact Events Request URL in Slack.
* **Connection unavailable:** retry the check. A temporary Slack failure is distinct from a revoked or invalid token.
* **Connected but no replies:** check event subscriptions, channel membership, model configuration and workspace access. The bot token being valid does not by itself verify every part of the agent workflow.

Older workspaces may still display a shared Notara app connection. They can continue using it during migration or replace it through this setup flow.