Skip to main content
Slack turns channels and threads into searchable memory. Connect on the Slack card (Integrations → Data sources) authorizes the Cognee Slack app for your workspace; a connected card shows the connection’s status and channel health, and Manage — or Reconnect, when the connection needs attention — opens the same dialog.

​
Choosing channels

Authorizing Slack reads nothing on its own: ingestion is opt-in per channel. The Manage dialog leads with the channels the bot can see, and you tick the ones to ingest, with a search box and bulk actions for a long list. Switching a channel on also ingests the history it already has. Until channels are routed the card says which of the two states it is in: Only the workspace owner can connect, manage, disconnect, or choose channels.

​
Linking your own Slack account

Connecting Slack authorizes the workspace, not you personally. To have /cognee-recall in Slack answer as you — from what your own Cognee account can see — run /cognee-link in Slack. It replies with a link to Connect your Slack account (route /link-slack), where Connect my account completes the pairing. Each link is valid for 10 minutes; when it expires or arrives malformed the page says so and tells you to run /cognee-link again. The page refuses to pair the wrong things, since it can only see which Slack member is asking:

​
Disconnecting

Disconnecting stops the reading. What Cognee already learned from the connection stays in memory — Slack’s disconnect does not offer to delete it, unlike Google Drive’s.
Self-hosted Cognee deployments run their own, separate Slack app against their own backend. Setup and usage are covered in the Slack integration guide, including importing selected channel and thread history with /cognee-import.