A week of a channel, in one read.
whyTwo hundred messages came in while you were out.
asksWhat did #sales decide while I was away?
Your own user token, from your workspace's approved app. It reads your channels, and speaks only as you.
team/tools/slack/slack.md channel ids, no tokenCatch up, post, share: three asks from a working week.
whyTwo hundred messages came in while you were out.
asksWhat did #sales decide while I was away?
whyAn announcement needs the right channel and the right facts.
asksPost the release notes to #announcements.
whyAn upload can fail without a word.
asksShare the incident report in #support.
Your token reads what you read. Posts, edits and deletions are shown to you first.
Full history pulled once to a file, then analysed.
Without it, history is filtered locally.
Followed to the end, since one call returns about 150.
You see the exact text, and where it goes, first.
Upload, then share; the AI checks it really appears.
Whose token, which workspace, one person, one channel.
A bot acts as the app. Every call here acts as you.
An admin approves the app once. You authorise it yourself. Posts change what the team reads, so each waits for your go.
A page names the workspace, the app, and channels by id.
The token sees what you see. Our server stores the channel map.
Read inside the call; never printed or logged.
New channels and guests go through a workspace admin.
Nothing goes out before you see it and say go.
Your app's scopes and your plan set them.
| Limit | What it means |
|---|---|
| Scopes decide | Outside them, calls answer missing_scope. |
| The free plan answers 90 days | Older history does not come back. |
Name the workspace and channels once. Claude Code and Codex then ask before they post as you.