OAuth Ready
← Guide library

OAuth launch guide

Slack

Post agent updates in customer workspaces

Researched draftChecked Oct 21, 2026Provider website ↗

At a glance

Moderate difficulty

A pilot can use unlisted distribution, while workspace admin controls and Marketplace review add separate gates.

Start hereChoose single-workspace test, unlisted multi-workspace pilot, or Marketplace listing.
Hands-on effort
Not measured
External wait
Unknown for workspace admins; up to 10 weeks for Marketplace functional review
Main blocker
Treating an unlisted pilot and Marketplace launch as the same path.

01

Scenario this guide covers

AudienceExternal customer workspaces

Registration pathCustom Slack app with OAuth distribution

  • The app posts as a bot
  • The team must choose between an unlisted pilot and Marketplace listing

02

Choose managed or custom

Available through ComposioOfficial source

Composio documents a managed Slack OAuth2 toolkit. Exact managed scopes and launch fit still need confirmation.

Choose custom when: Use a custom Slack app for your own identity, requested scopes, distribution, and Marketplace path.

03

Before you start

01

Slack development workspace and permission to create/install appsAlways

Developer
02

HTTPS redirect URL and install landing pathMulti-workspace OAuth

Developer
03

External-workspace testing and installation on at least 10 active workspacesMarketplace submission

Developer + customers
04

Install/OAuth/use/uninstall demonstration videoMarketplace submission

Developer

04

Permissions in plain language

chat:write

Post messages as the app’s bot userMatches the example capability of posting agent updates.

Bot scopeSource ↗

05

Your setup path

1
Developer

Choose the launch path

Set the correct target before preparing distribution evidence.

Choose development workspace, unlisted OAuth distribution, or Marketplace listing.

Expected result: A launch target with the relevant gates.Open official page ↗Official source · Slack
2
Developer

Create and install the app

Prove the bot can post in a controlled workspace.

Create the Slack app, add chat:write under OAuth & Permissions, and install it in the development workspace.

Expected result: A bot installation for testing; keep credentials server-side.Open official page ↗Official source · Slack
3
Developer

Test the OAuth install

Verify redirect and install behavior outside the original workspace.

Run the OAuth flow in an external test workspace and verify post and uninstall behavior.

Expected result: A recorded cross-workspace test. This project has not observed it yet.Open official page ↗Official source · Slack
4
Developer → customer admin / Slack

Distribute or submit

Open the chosen path to customers.

Enable distribution for an unlisted pilot, or prepare and submit the Marketplace package when listing is required.

Expected result: Install access or a Slack review decision, depending on path.Open official page ↗Official source · Slack

06

Review and waiting

RequirementPath dependent
Decision ownerCustomer admins and/or Slack
Published / known waitAdmin wait unknown; Slack documents preliminary feedback up to 10 business days and functional review up to 10 weeks for new Marketplace submissions

Customer admin approval depends on workspace policy; Marketplace review applies to a listing.

Prepare this evidence

  • External workspace end-to-end test
  • Active workspace eligibility for Marketplace
  • Install and usage demonstration video

07

When you get blocked

A customer cannot install the app.+

Likely cause: Their workspace may restrict app installation or require admin approval.

Recovery: Ask their workspace admin to review the installation request.

Official help ↗
The app is not eligible for Marketplace submission.+

Likely cause: The active-workspace or external-testing prerequisite may not be met.

Recovery: Run an unlisted pilot and collect the documented eligibility evidence first.

Official help ↗

08

Who does what

Agent

Can prepare

  • Map actions to Slack scopes
  • Prepare distribution and review checklists
You

Must complete

  • Create, configure, and test the app
  • Collect authentic install evidence and submit
Provider

Decides

  • Customer admins decide restricted installs
  • Slack decides Marketplace listing

09

Sources and limits

01

App settings quickstartSlack · checked 2026-10-21

↗02

Installing with OAuthSlack · checked 2026-10-21

↗03

Distribute your appSlack · checked 2026-10-21

↗04

Slack Marketplace review guideSlack · checked 2026-10-21

↗
What we did not verify
  • No Slack app, install, or Marketplace submission was completed by this project.
  • Workspace-admin timing is not published and remains unknown.