Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: add Slack approval and rate limit difference between the two managed apps
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Jeevesh Jain committed
Nov 16, 2026 at 09:35 UTC
40ab827d52b907ae92ed9ac8dc05d862658be10c
2 files changed
+10
-8
docs/content/docs/authentication/custom-app-vs-managed-app.mdx
+1
-1
@@ -9,7 +9,7 @@ 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.
12
+Slack has two managed apps with different rate limits and 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
docs/content/toolkits/managed-auth.mdx
+9
-7
@@ -26,21 +26,23 @@ See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for
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.
29
+Slack is the one toolkit with two Composio managed apps. You don't register anything with Slack for either one. Slack has approved Standard but not Legacy. The two apps get different Slack rate limits and receive different triggers.
30
31
-| App | Default | Triggers |
32
-|---|---|---|
33
-| Standard | Yes | Every Slack trigger except the four message triggers below |
34
-| Legacy | No | Every Slack trigger |
31
+| App | Default | Approved by Slack | Slack rate limits | Triggers |
32
+|---|---|---|---|---|
33
+| Standard | Yes | Yes | Higher | Every Slack trigger except the four below |
34
+| Legacy | No | No | Lower | Every Slack trigger |
35
36
-Slack has reviewed the Standard app. It does not receive these message triggers:
36
+Slack gives approved apps higher limits on its API methods than unapproved ones. See [Slack's rate limits](https://docs.slack.dev/apis/web-api/rate-limits) for the numbers.
37
+
38
+Standard does not receive these message triggers:
39
40
- `SLACK_CHANNEL_MESSAGE_RECEIVED`
41
- `SLACK_DIRECT_MESSAGE_RECEIVED`
42
- `SLACK_RECEIVE_BOT_MESSAGE`
43
- `SLACK_RECEIVE_MESSAGE`
44
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.
45
+Keep Standard unless your product reacts to new Slack messages. Pick Legacy when you need one of these four triggers and your traffic fits under the lower limits.
46
47
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).
48