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, 04:45 UTC
docs: explain Slack's two managed apps
Slack has a Standard managed app (default, reviewed by Slack) that does not receive the four message triggers, and a Legacy app that receives every trigger. Add a section with a stable anchor so the dashboard can link to it, and cross-link it from Managed vs custom auth. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Jeevesh Jain committed
Nov 16, 2026 at 09:32 UTC
87b2c59b43d910c5f72add07d3bdbe00e0fd2807
2 files changed
+22
docs/content/docs/authentication/custom-app-vs-managed-app.mdx
+2
@@ -9,6 +9,8 @@ Composio supports two ways to authenticate users with toolkits.
9
- **[Composio managed apps](/toolkits/managed-auth)**: Composio registers and maintains OAuth apps for popular toolkits such as GitHub, Gmail, and Slack. You do not need to register your own OAuth app.
10
- **Custom auth configs**: You provide your own OAuth app, API key, bearer token, or other credentials and tell Composio to use them for a toolkit.
11
12
+Slack has two managed apps that receive different triggers. See [Slack managed apps](/toolkits/managed-auth#slack-managed-apps) to pick one.
13
+
14
This page covers when to use each, how to create a custom auth config, and how to wire it into a session.
15
16
Both options use Composio to store and refresh connected-account credentials. Choosing your own OAuth app changes app ownership, branding, scopes, and provider quota, not [token custody](/docs/security/token-custody#oauth-app-ownership-and-token-custody).
docs/content/toolkits/managed-auth.mdx
+20
@@ -24,6 +24,26 @@ You can also provide your own OAuth app to show your app name on the consent scr
24
25
See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for setup steps and trade-offs.
26
27
+## Slack managed apps
28
+
29
+Slack is the one toolkit with two Composio managed apps. Neither needs an app registered with Slack. They differ in which triggers they receive.
30
+
31
+| App | Default | Triggers |
32
+|---|---|---|
33
+| Standard | Yes | Every Slack trigger except the four message triggers below |
34
+| Legacy | No | Every Slack trigger |
35
+
36
+Slack has reviewed the Standard app. It does not receive these message triggers:
37
+
38
+- `SLACK_CHANNEL_MESSAGE_RECEIVED`
39
+- `SLACK_DIRECT_MESSAGE_RECEIVED`
40
+- `SLACK_RECEIVE_BOT_MESSAGE`
41
+- `SLACK_RECEIVE_MESSAGE`
42
+
43
+Keep Standard if your product doesn't react to new Slack messages. Pick Legacy when you need any of these four triggers and still want Composio to provide the OAuth app.
44
+
45
+Use your own Slack app when you need message triggers and your app name on the Slack consent screen, or scopes that neither managed app requests. Follow the [Slack OAuth guide](https://composio.dev/auth/slack), then [create a custom auth config](/docs/authentication/custom-app-vs-managed-app#create-a-custom-auth-config).
46
+
47
## Find an OAuth toolkit
48
49
Search for a toolkit to check whether Composio provides a managed OAuth app.