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, 23:30 UTC
docs(changelog): generalize the V2 adoption recommendation
Drop the Slack-specific "private channels and DMs" framing — V2 covers many toolkits going forward. Tighten to a short, generic recommendation that names the benefits as a quick list and points back to the full rationale above. _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
Apr 18, 2026 at 21:57 UTC
f16fcd99992297ae04bc2a8bc2572e22d595650a
1 file changed
+1
-1
docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+1
-1
@@ -158,4 +158,4 @@ You only need to set up a V2 webhook endpoint in two cases:
158
1. **You want to use one of the new V2 trigger slugs** (e.g. `SLACK_CHANNEL_MESSAGE_RECEIVED`, `SLACK_DIRECT_MESSAGE_RECEIVED`). A V2 endpoint is required at setup; without one, the upsert returns `400`.
159
2. **You want to move an OAuth app that's currently shared across multiple projects or organizations onto V2.** Pick the project that should own it on V2 and set up an endpoint there, or register separate OAuth apps per project (see [Heads up: OAuth apps are project-scoped on V2](#heads-up-oauth-apps-are-project-scoped-on-v2)).
160
161
-Even if neither applies today, we recommend moving your active OAuth apps to V2 when it's convenient — you'll pick up signature verification, per-user authorization for private channels and DMs, and per-project ingress isolation along the way.
161
+Even outside these two cases, we recommend moving your OAuth apps to V2 at your own pace. Every endpoint you migrate inherits the signature verification, ingress isolation, and per-user authorization called out above.