@devries-cameron20 / composio-1 / commits / 51cb0934f
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): rewrite backward-compat tail and drop boilerplate sections

Reframe the closing of the V2 changelog around two things customers need to walk away with: 1. A strong, plain reassurance that nothing breaks (URLs, slugs, payload shapes, no data migration). 2. The two specific cases that *do* require a V2 endpoint — using a new V2 trigger slug, or moving a shared-across-projects OAuth app onto V2 — with a definitive "no action required" if neither applies. Drop the Availability and Support sections — both were unique to this entry and not present in other changelogs. _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 18, 2026 at 21:47 UTC 51cb0934f4f8860b43b3cacb165c07751d4d2bd9
1 file changed +9 -9
docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+9 -9
@@ -148,16 +148,16 @@ Your V1 endpoints are unaffected. Any OAuth app you leave on V1 continues to wor
148
149 ## Backward compatibility
150
151 -- V1 ingress (`/api/v3/trigger_instances/{toolkit}/{project_id}/handle`) is **not deprecated**.
152 -- All existing trigger slugs — every `SLACK_RECEIVE_*`, `SLACKBOT_*`, and equivalent legacy slug across toolkits — continue to route through V1 unchanged.
153 -- No server-side data migration touches existing trigger instances.
154 -- V1, V2, and V3 outbound webhook payload formats are unaffected.
151 +**Everything you have today keeps working — same URLs, same trigger slugs, same payload shapes, no data migration.**
152
156 -## Availability
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.
157
158 -V2 is opt-in. Slack is the first toolkit available; HubSpot, Linear, and other app-level toolkits will follow the same pattern and be announced in their own changelog entries. There is no migration deadline — adopt V2 when you need its features.
158 +You only need to set up a V2 webhook endpoint in two cases:
159
160 -## Support
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`.
161 +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)).
162
162 -- [Discord](https://discord.gg/composio)
163 -- [support@composio.dev](mailto:support@composio.dev)
163 +If neither applies to you, no action is required.