@devries-cameron20 / composio-1 / commits / ffd2cef8b
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.

docs(changelog): Slack Standard and Legacy managed apps (#5468)

<!-- claude-slack-attribution --> _Requested by **Bharath Singh** · [Slack thread](https://composioworkspace.slack.com/archives/C09F5RR3KS9/p1794902956321619)_ ## Summary **Before:** Slack on Composio managed auth had a single managed app, now called Legacy, and there was no higher-limit option. **After:** A second, Slack-approved Standard app with higher rate limits is available as an opt-in via `managed_app_id`. Legacy stays the default and keeps receiving every Slack trigger. This adds a changelog entry so developers learn about the new option, how to select it, and which triggers each app receives. ## Changes - Adds `docs/content/changelog/11-17-26-slack-managed-apps.mdx`. Facts come from the #ship post, the Slack toolkit docs and the `postAuthConfigs` API reference. ## Type of change - [x] Documentation ## Additional context The behavior of existing Slack connections is intentionally not covered in the entry because it is unconfirmed. --- _Generated by [Claude Code](https://claude.ai/code)_ Co-authored-by: Claude <noreply@anthropic.com>

claude[bot] committed Nov 19, 2026 at 11:42 UTC ffd2cef8b41d8287e1bc800ec9801996c7adea71
1 file changed +17
docs/content/changelog/11-17-26-slack-managed-apps.mdx new
+17
@@ -0,0 +1,17 @@
1 +---
2 +title: 'Higher rate limits for Slack on Composio managed auth'
3 +description: 'Slack now has two Composio managed apps: Standard, approved by Slack with higher rate limits, and Legacy, which receives every Slack trigger.'
4 +date: '2026-11-17'
5 +---
6 +
7 +Composio now offers two managed apps for the Slack toolkit. The new Standard app is approved by Slack, so it gets higher Slack API rate limits than an unapproved app, and it is opt-in. The existing app is now called Legacy, remains the default, and keeps receiving every Slack trigger. You don't register anything with Slack for either one.
8 +
9 +### What's new
10 +
11 +- **Standard managed app (opt-in).** Approved by Slack, with higher rate limits. Select it with `managed_app_id`. It receives every Slack trigger except `SLACK_CHANNEL_MESSAGE_RECEIVED`, `SLACK_DIRECT_MESSAGE_RECEIVED`, `SLACK_RECEIVE_BOT_MESSAGE` and `SLACK_RECEIVE_MESSAGE`.
12 +- **Legacy managed app.** Not approved by Slack, so it has lower rate limits. It receives every Slack trigger, including the four message triggers above. This is still the default.
13 +- **`managed_app_id` on auth configs.** When you create an auth config with `type: "use_composio_managed_auth"`, pass `managed_app_id` to choose the managed app. If you omit it, the auth config uses the Legacy app. List the available IDs under `composio_managed_auth[].managed_app_id` in `GET /api/v3/toolkits/slack`. The field is also returned on the auth config.
14 +
15 +### Which one to use
16 +
17 +Use Standard unless your product reacts to new Slack messages. Pick Legacy when you need one of the four message triggers and your traffic fits under its lower limits. If you need message triggers and your own app name on the Slack consent screen, or scopes neither managed app requests, use your own Slack app. See the [Slack toolkit page](/toolkits/slack), the [create auth config API reference](/reference/api-reference/auth-configs/postAuthConfigs) and [Avoid and recover from rate limits](/docs/poc-to-prod/avoid-rate-limits).