Slack

Capped

slack.comSourcedUpdated 27 Oct 2026 · yesterday

Any workspace can install your Slack app over OAuth on the same day: you create the app, complete the distribution checklist and turn on public distribution, with no review. The catch is that unlisted apps get severe rate limits on reading message history (conversations.history and conversations.replies drop to 1 request per minute). Lifting that limit means getting into the Slack Marketplace, which requires 10+ active installs and a review that can take up to about 12 weeks.

Your work: 1–3 h
Waiting on Slack: None
First user connects: Today, in about 30 minutes

2 not confirmed 8 sources Why this tier How did it go?

.md JSON

Use with your agent

Set up a Slack OAuth app for our integration, as far as you can.
Guide: https://oauth-guide.akshatsethi.com/apps/slack.md (updated 27 Oct 2026)

Capped. Hands-on work: 1–3 h. Waiting on Slack: none.

Check these exist first:
- A Slack workspace you can sign in to [human]
- An HTTPS redirect URI [agent]

Needed later, not now:
- A working OAuth v2 flow (for beta)
- 10+ active workspace installs (for launch)
- Demo video and reviewer test account (for launch)

Steps, in order:
1. [human] Create a Slack app
2. [agent] Add your redirect URI and scopes. Under OAuth & Permissions, add your redirect URI (HTTPS) and the bot scopes and user scopes your integration needs. Request only what you use, because workspace admins may have to approve the app. Watch out: If you configure several redirect URLs, send the same redirect_uri in the authorize call and in oauth.v2.access, or you'll get bad_redirect_uri.
3. [human] Put the client ID and secret into your OAuth client
4. [agent] Test an install on your own workspace. Run the OAuth flow against your development workspace and confirm that a token comes back. Watch out: Installing in any other workspace before you enable distribution fails with invalid_team_for_non_distributed_app.
5. [human] Activate public distribution
6. [human] Get 10+ active workspace installs
7. [human] Submit to the Slack Marketplace
8. [provider] Wait for preliminary and functional review (wait 2–12 weeks)

Rules:
- Do [agent] steps yourself. Steps in Slack's dashboard need a browser I'm signed in to; without one, give me the exact clicks and values instead, then carry on with the code.
- At each [human] or [provider] step, stop and tell me exactly what's needed.
- Never put client secrets in chat, code or commits. I paste them into our OAuth client or secret manager myself.
- Claims marked Inferred or low confidence in the guide are unverified. Check them and tell me what you find.
- If the guide doesn't match what you see (a page, field or requirement), tell me and report it so it gets fixed: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "slack", "step": 2, "message": "what you saw"} (step is optional), or call the report_problem MCP tool. Never put secrets or personal data in a report.
- When setup ends (users can connect, or it's waiting on Slack's review) or you can't get past a step, report how it went so the guide improves: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "slack", "outcome": "worked" | "waiting" | "stuck", "step": 3, "message": "what happened"}, or call the report_setup MCP tool. Stopping for me at a [human] step isn't stuck: don't report that.
- Finish with what's done, the redirect URI and scopes used, and what's left before public launch.

Paste into Claude Code, Cursor or any agent.

Slack

Plan

SetupBefore you start

BuildYour workspace

BetaUnlisted public distribution

LaunchSlack Marketplace

Why capped

Scopes

When you get stuck

Not confirmed

Sources

Feedback

Slack

Plan

SetupBefore you start

BuildYour workspace

BetaUnlisted public distribution

LaunchSlack Marketplace

Why capped

Scopes

When you get stuck

Not confirmed

Sources

Feedback