Cogito + Slack
AI that lives in Slack and reasons across it.
Slack is where work happens. Cogito is a Slack app: it joins channels, listens to threads, and reasons across the entire workspace history with full per-user permission inheritance. Personal Slack connections coming soon.
Try Cogito FreeLive in under 5 minutes. No card required.
Built deep, not via MCP
Cogito's Slack integration is a first-class API connection with the depth, reliability, and permission inheritance most AI tools cannot match.
Native Slack app, not a polling integration or a third-party bridge
Real-time message ingestion via Slack Events API
Threaded reply support, including private thread state
User permission inheritance - channels, private channels, user groups all respected
Personal, organizational, or both
Cogito's Slack integration ships with the connection model that fits your team. The layering story is the differentiator.
Organizational mode
Admin connects once. Whole team inherits.
Slack is the team interface. Cogito as a Slack app means questions happen where work happens, no tool switching, no separate UI. Permission inheritance means each user only ever sees Slack content they could read directly.
Reads
- •Messages and threads in channels Cogito is invited to
- •Workspace metadata: channels, members, user groups
- •Reactions, file uploads, and message edit history
- •Each user is scoped to channels they have access to
Acts on
- •Post messages and threaded replies
- •Send DMs and group DMs
- •Add reactions
- •Create channels (when admin enables)
- •Invite users to channels
Real-time triggers
Webhooks fire the instant something changes in Slack. Build workflows that react in seconds, not minutes.
Message posted in a watched channel
Example use: When a customer name is mentioned in #customer-feedback, attach the customer context from your CRM and post it in-thread.
App mention
Example use: A user @-mentions Cogito to start a conversation, which lands in private thread state by default.
Channel created
Example use: When a new channel is created matching the pattern #incident-*, auto-add Cogito and the on-call engineer.
Reaction added
Example use: When the 🐛 reaction is added to a message, auto-create a Linear bug with the message as the description.
User joined channel
Example use: DM new channel members with a one-paragraph context summary of what the channel is about and recent decisions.
Common workflows
Concrete day-to-day moments where Cogito + Slack earns its keep.
Ask anything in any channel
A sales rep types in #sales: "@Cogito what was the latest with Acme on pricing?" Cogito searches the channel history, the Intercom thread tied to Acme, and the Notion account brief, then posts a synthesized answer in-thread. No tool switching, no copy-paste from five different surfaces.
Auto-respond to common questions in #support
Set up a workflow: when a customer-facing question is asked in #support that matches the pattern of a known issue, Cogito drafts a reply citing the relevant Notion runbook and the latest Linear status, and posts it for the human to approve before sending.
Reaction-driven Linear tickets
The team agrees on a convention: any message with the 🐛 reaction becomes a Linear bug. Cogito watches the reaction event, creates the Linear issue with the message body, the channel context, and the original poster as the reporter, and replies in-thread with the issue link. Triage happens at the speed of an emoji.
New-member onboarding briefing
When a new engineer joins #engineering, Cogito DMs them a one-paragraph summary of the most-discussed projects in the last 30 days, the team conventions documented in Notion, and the open Linear issues that need fresh eyes. Onboarding starts at minute one, not week one.
Permission granularity
You pick the OAuth scopes at connect time - more access unlocks more capability, less access keeps Cogito narrowly scoped
Each user inherits their native Slack channel access live
Private channels remain invisible to Cogito unless the user has access AND has invited Cogito
DMs are never read in organizational mode - only the user's own queries
Per-channel scoping (some channels read-only, some excluded entirely)
Setup time
Under 5 minutes
- 1
Open Cogito settings, navigate to Integrations, Organization
- 2
Click Add to Slack
- 3
Authorize the Cogito Slack app for your workspace
- 4
Invite Cogito to the channels you want it active in
- 5
Configure per-channel scope from the Cogito Slack settings
OAuth scopes / permissions
You choose which scopes to grant at connect time. Cogito's capability is bounded by exactly what you authorize. Grant read-only at first, expand later as you build trust.
- channels:history, channels:read, channels:join
- chat:write, im:write
- reactions:read, reactions:write
- users:read, team:read
Common questions
Still have questions?
Get in touchDon't see what you need?
Cogito ships new integrations on customer request, typically within about 3 days. Sign up and ask.
Last reviewed