Sentra for Slack
Sentra reads the Slack channels its app is added to and turns the conversation into facts with an owner, a source and a time, so decisions made in Slack reach every agent and person who is allowed to see them.
What Sentra syncs
- Messages in public and private channels the Sentra app is a member of, grouped per channel per day
- Direct and group messages with the Sentra app
- Channel membership, users and user groups, used to enforce access
How it syncs
Slack's Events API delivers new messages as they are posted. Sentra processes them into memory every hour and runs a daily collection to catch anything missed.
Permissions Sentra requests
Bot scopes for reading channel, private channel, direct and group message history (channels:history, groups:history, im:history, mpim:history), reading channels and users (channels:read, groups:read, users:read, users:read.email, usergroups:read), search (search:read.public, search:read.private) and posting replies (chat:write). Private channel history from users' own access is a separate, optional consent that an organization admin turns on.
Who can see what
A person, or an agent acting for them, only sees facts from Slack channels that person can access. Public channel content is visible to members of the workspace. Admins get no bypass.
Setup
An admin installs the Sentra Slack app from Settings, then adds it to the channels Sentra should learn from. People can also ask Sentra questions directly in Slack.
Using it from agents
Everything Sentra learns from Slack is available to ChatGPT, Claude, Cursor and internal agents through the Sentra MCP server and the REST API, with the same access rules applied to every request.