docs: add changelog for slackbot bot-compatible actions

[Karthikeya-Meesala]

Summary

Adds changelog entry for the slackbot toolkit update that filters actions to only include bot-compatible ones.

• Slackbot toolkit now includes only 89 actions (down from 155)
• Removed 62 admin-only actions that require user tokens
• All 9 triggers remain unchanged

Related: https://github.com/ComposioHQ/mercury/pull/15117

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Feb 21, 2026 0:05am

[claude]

Claude finished @Karthikeya-Meesala's task in 1m 13s —— View job

---

PR Review

• Gather context
• Read docs reviewer guidelines
• Review changed files
• Post review feedback

---

File: docs/content/changelog/02-20-26-slackbot-actions.mdx

Frontmatter checks:

• title ✅
• date: "2026-02-20" (YYYY-MM-DD) ✅

One issue found:

The reviewer guidelines require that breaking changes include before/after code examples. Removing 62 actions from the Slackbot toolkit is a breaking change — developers using any of the removed admin/audit/SCIM actions via slackbot will have their calls fail.

The file directs affected users to "use the full Slack toolkit with appropriate user token authentication," but doesn't show how. A developer who was using SLACK_ADMIN_ADD_EMAIL_TO_WORKSPACE through the Slackbot toolkit, for example, would not know what to change.

Fix:

Add a migration snippet at the bottom of the "Removed Actions" section:

### Migration

If you were using any of the removed actions, switch to the full Slack toolkit and supply a user token:

```typescript
// Before (Slackbot toolkit — admin actions no longer available)
const tools = await composio.tools.get('user-id', {
  toolkits: ['slackbot'],
  tools: ['SLACK_ADMIN_ADD_EMAIL_TO_WORKSPACE'],
});

// After (full Slack toolkit with user token)
const tools = await composio.tools.get('user-id', {
  toolkits: ['slack'],
  tools: ['SLACK_ADMIN_ADD_EMAIL_TO_WORKSPACE'],
});

Ensure the connected account for the slack toolkit uses a user token (not a bot token) with the required admin scopes.
``

[Fix this →](https://claude.ai/code?q=In%20docs%2Fcontent%2Fchangelog%2F02-20-26-slackbot-actions.mdx%20on%20branch%20docs%2Fchangelog-slackbot-02-20%2C%20add%20a%20Migration%20section%20with%20before%2Fafter%20TypeScript%20code%20examples%20showing%20how%20to%20switch%20from%20the%20slackbot%20toolkit%20to%20the%20full%20slack%20toolkit%20for%20admin-level%20actions.%20The%20before%20example%20should%20use%20toolkits%3A%20%5B%27slackbot%27%5D%20with%20an%20admin%20action%2C%20and%20the%20after%20example%20should%20use%20toolkits%3A%20%5B%27slack%27%5D%20with%20a%20note%20about%20user%20token%20and%20admin%20scopes.&repo=ComposioHQ%2Fcomposio)

[haxzie]

Add the toolkit version here on which the changes are reflected

[Karthikeya-Meesala]

will add once merged into prod.

[claude]

Claude finished @Sushmithamallesh's task in 55s —— View job

---

PR Review

• Read docs reviewer guidelines
• Get PR diff
• Review changed file
• Post review feedback

---

File: docs/content/changelog/02-20-26-slackbot-actions.mdx

Frontmatter checks:

• title ✅
• date: "2026-02-20" (YYYY-MM-DD) ✅

One issue found:

The reviewer guidelines require that breaking changes include before/after code examples. Removing 62 actions from the Slackbot toolkit is a breaking change — any developer using admin/audit/SCIM actions via the slackbot toolkit will have their calls fail after this update.

The file says "use the full Slack toolkit with appropriate user token authentication" but doesn't show how. A developer using SLACK_ADMIN_ADD_EMAIL_TO_WORKSPACE through the Slackbot toolkit would not know what to change.

Fix: Add a migration section showing what to change:

### Migration

If you were using any of the removed actions, switch to the full Slack toolkit with a user token:

```typescript
// Before (Slackbot toolkit — admin actions no longer available)
const tools = await composio.tools.get('user-id', {
  toolkits: ['slackbot'],
  tools: ['SLACK_ADMIN_ADD_EMAIL_TO_WORKSPACE'],
});

// After (full Slack toolkit with user token)
const tools = await composio.tools.get('user-id', {
  toolkits: ['slack'],
  tools: ['SLACK_ADMIN_ADD_EMAIL_TO_WORKSPACE'],
});

Ensure the connected account for the slack toolkit uses a user token (not a bot token) with the required admin scopes.
``

[Fix this →](https://claude.ai/code?q=In%20docs%2Fcontent%2Fchangelog%2F02-20-26-slackbot-actions.mdx%20on%20branch%20docs%2Fchangelog-slackbot-02-20%2C%20add%20a%20Migration%20section%20after%20the%20%22Removed%20Actions%22%20section%20with%20before%2Fafter%20TypeScript%20code%20examples%20showing%20how%20to%20switch%20from%20toolkits%3A%20%5B%27slackbot%27%5D%20to%20toolkits%3A%20%5B%27slack%27%5D%20for%20admin-level%20actions.%20Include%20a%20note%20about%20needing%20a%20user%20token%20with%20admin%20scopes.&repo=ComposioHQ%2Fcomposio)