> 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/connectors/slack.md).

# Slack

The Slack connector gives the Notara agent access to your Slack workspace's data and messaging capabilities — beyond the base bot integration. While the base bot lets users talk to the agent, the Slack connector lets the agent *act* in Slack: look up messages, post to any channel, and manage users.

## What It Enables

| Tool                        | Capability | Description                                |
| --------------------------- | ---------- | ------------------------------------------ |
| `slack_get_channel_history` | `read`     | Retrieve recent messages from a channel    |
| `slack_search_messages`     | `read`     | Full-text search across workspace messages |
| `slack_get_user_info`       | `read`     | Look up a team member by name or ID        |
| `slack_list_channels`       | `read`     | List all channels in the workspace         |
| `slack_post_message`        | `write`    | Post a message to any channel              |
| `slack_send_dm`             | `write`    | Send a direct message to a user            |
| `slack_create_channel`      | `write`    | Create a new Slack channel                 |
| `slack_invite_to_channel`   | `write`    | Invite a user to a channel                 |

Read tools execute immediately. Write tools require approval by default (configurable from **Settings → Permissions**).

## Setup

First connect your customer-owned Slack app through **Connections → Optional Slack connection**. Follow [Connecting your own Slack app](/notara-docs/getting-started/slack-setup.md) for the manifest, credential validation and activation steps.

Slack tools and the conversational bot are separate surfaces. Availability depends on the enabled connector, its credentials and granted Slack permissions. Creating the app does not grant access to every Slack API or channel. Review the tools and permission controls in your workspace before using them.

## Usage Examples

**Summarize recent activity in #engineering:**

```
@Notara What's been discussed in #engineering today?
```

**Find a specific decision:**

```
@Notara Search Slack for the discussion about switching to Postgres 17.
```

**Post a summary to a channel:**

```
@Notara Post a summary of this week's Linear issues to #engineering.
```

(This will trigger an approval request since `slack_post_message` is a write tool.)

**Look up a team member:**

```
@Notara What's Amir's Slack handle?
```

## Permissions

Because this connector can read message history and post to channels, it should be enabled thoughtfully. Recommended configuration:

* **Read tools** — leave as `open` (default). Channel history reads are useful for context and summaries.
* **Write tools** — leave as `requires_approval` (default) in general channels. In a trusted engineering or ops channel, you might loosen to `open` for specific tools like `slack_post_message` if your team is comfortable with agent-initiated posts.

To adjust: go to **Settings → Permissions**, find the Slack tools, and set the permission level.

## Privacy Considerations

The Slack connector can access message history in any channel the Notara bot has been invited to. It cannot access channels or DMs it hasn't been invited to — Slack's permission model enforces this at the API level.

Message content retrieved via this connector is passed to your LLM (via your BYOK key) as context. It is not stored in Notara's database unless you explicitly save it to a library document.