@devries-cameron20 / composio Mirror · read-only / commits / 138b4d075
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 22:15 UTC

docs(toolkits/slack): add OAuth install/approval FAQs

Add five FAQs covering the most common Slack OAuth install friction points: the "not listed in Marketplace" prompt, when workspace owner approval is required, "submit a request" approval flows, completing the connection without owner involvement, and the recommended fix (custom OAuth app). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: Uday Sidagana <uday@composio.dev>

Zen committed Apr 30, 2026 at 18:12 UTC 138b4d0757026658b91c9537c40c962047103d60
1 file changed +23
docs/content/toolkits/faq/slack.md
+23
@@ -10,6 +10,29 @@ Composio executes API calls on behalf of your connected account. All data is enc
10
11 For a step-by-step guide on creating and configuring your own Slack OAuth credentials with Composio, see [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
12
13 +## Why do users see "This app isn't listed in the Slack Marketplace…" during install?
14 +
15 +This appears when a workspace **member** tries to install a non-Marketplace app and the workspace has **"Require apps from Slack Marketplace"** enabled. To resolve, either have a workspace **owner** install/authorize the app, disable **"Require apps from Slack Marketplace"** in the workspace's app management settings, or — recommended — use your own OAuth app credentials. See [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
16 +
17 +## Do I have to be a Workspace Owner to install the app?
18 +
19 +Only if the workspace blocks non-Marketplace apps. If **"Require apps from Slack Marketplace"** is enabled, then yes — a workspace owner must install our app. Otherwise, a member may proceed with the install themselves.
20 +
21 +## Why am I being asked to submit a request during auth?
22 +
23 +The workspace has **"Require approved apps"** enabled, so Slack is asking an admin or owner to approve the install before it can be completed. An admin must approve the request, or the setting must be disabled, before the connection can finish.
24 +
25 +## How can a workspace member complete the connection without asking for permissions or approvals?
26 +
27 +There are two ways:
28 +
29 +- Disable both **"Require apps from Slack Marketplace"** and **"Require approved apps"** in the workspace's app management settings.
30 +- Use the workspace's own OAuth app credentials (recommended — see below).
31 +
32 +## What's the recommended solution for Slack install/approval friction?
33 +
34 +Use your own OAuth app credentials. It's the safest option and avoids repeated owner/admin involvement on every install. See [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
35 +
36 ## What is the difference between Slack and Slackbot toolkits?
37
38 Slack is for workspace-level API access (channels, files, users) while Slackbot is bot-centric (messaging, interactivity). Slack triggers cover workspace events; Slackbot covers bot entry points like app mentions, DMs, and slash commands. Slack can post as the app; Slackbot posts as the bot user.