Slack

SLACK · MESSAGING

Channels, messages, and files — with the person’s identity on the post.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

slack_get_connection_infoREAD

Get Slack connection information including workspace name, bot user ID, and connection status.

no provider scope

slack_get_dm_messagesREAD

Get recent messages from a direct message (DM) conversation.

im:historyim:read

slack_get_group_messagesREAD

Get recent messages from a private channel or group.

groups:historygroups:read

slack_get_messagesREAD

Get recent messages from a Slack channel.

channels:historychannels:read