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	Error		Feb 20, 2026 9:04pm

[claude]

Claude finished @Karthikeya-Meesala's task in 2m 36s —— View job

---

PR Review

• Gather context and understand request
• Read docs reviewer guidelines (docs/.claude/guides/changelog.md)
• Get PR diff
• Apply review checklist
• Post review findings

---

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

Format Checklist

Rule	Status
Frontmatter has title and date (YYYY-MM-DD)	✅
No # top-level heading (title auto-renders)	✅
Sections use ### headings	✅
No emojis	✅
File naming convention (MM-DD-YY-suffix.mdx)	✅

Issue: Missing Warning Callout for Breaking Change

Removing 62 previously available actions is a user-facing breaking change. Anyone who built integrations using admin.*, audit.*, or SCIM actions via the Slackbot toolkit will have those actions silently disappear.

The changelog guide specifies that breaking changes should use <Callout type="warn">. The comparable 02-12-26-twitter-managed-credentials-removal.mdx entry uses this pattern with an "Action Required" notice. This entry should follow the same pattern.

The migration note at the bottom is good but needs to be elevated to a callout. Suggested addition after the intro paragraph:

<Callout type="warn">
**Action Required**

If you were using any of the 62 removed admin actions (e.g. `SLACKBOT_ADMIN_*`, `SLACKBOT_AUDIT_*`) via the Slackbot toolkit, those actions are no longer available. Switch to the full Slack toolkit with a user token to continue using admin-level functionality.
</Callout>

Fix this →

Minor Notes

• The description frontmatter field is not in the template but is consistent with several other recent entries (e.g. 02-03-26.mdx, 02-12-26-twitter-managed-credentials-removal.mdx) — no change needed.
• Content is clear and well-structured; the table summarizing counts is a nice touch.

---

Overall: One change requested (warning callout). Otherwise the entry is well-written and correctly formatted.

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Changelog file in wrong directory

High Severity

The changelog file is being created in docs/content/changelog/ but the documentation configuration in fern/docs.yml line 128 specifies changelogs should be in fern/pages/src/changelog/. This file won't be discovered or displayed in the documentation system, making the changelog invisible to users.

 

[cursor]

Incorrect action count arithmetic

Medium Severity

The action counts don't add up correctly. Line 7 states there were previously 155 total actions, and the table shows 89 bot-compatible plus 62 removed actions. However, 89 + 62 = 151, not 155. There's a discrepancy of 4 actions that are unaccounted for in the documentation.

 

[cursor]

Wrong file format and naming convention

Medium Severity

The changelog file uses .mdx extension with frontmatter (YAML metadata), but all existing changelog files in fern/pages/src/changelog/ use .md extension without frontmatter and follow the naming pattern MM-DD-YY.md. This file should be 02-20-26.md instead of 02-20-26-slackbot-actions.mdx and shouldn't include the frontmatter block.