@devries-cameron20 / composio-1 / commits / c0ce6ab73
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): trim backward-compat section and recommend V2 adoption

- Drop the third and fourth bullets ("payload formats unchanged" and "no server-side migration") — both restate the lead-in sentence. - Drop the "with a suggestedFix" detail from case 1; the 400 alone is enough. - Replace the "no action required" closer with a forward-leaning recommendation to move active OAuth apps to V2 when convenient, citing the concrete benefits (signature verification, per-user authz, per-project ingress isolation). _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 18, 2026 at 21:56 UTC c0ce6ab731ec4361b61805491b2fb0b9b8499888
1 file changed +2 -4
docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+2 -4
@@ -152,12 +152,10 @@ Your V1 endpoints are unaffected. Any OAuth app you leave on V1 continues to wor
152
153 - The V1 ingress URL (`/api/v3/trigger_instances/{toolkit}/{project_id}/handle`) is not deprecated.
154 - Every existing trigger slug — `SLACK_RECEIVE_*`, `SLACKBOT_*`, and the equivalent legacy slugs on other toolkits — continues to route through V1.
155 -- V1, V2, and V3 outbound webhook payload formats are unchanged.
156 -- No server-side migration touches your existing trigger instances or auth configs.
155
156 You only need to set up a V2 webhook endpoint in two cases:
157
160 -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` with a `suggestedFix`.
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
163 -If neither applies to you, no action is required.
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.