@devries-cameron20 / composio Mirror · read-only / commits / 373b050d0
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 23:30 UTC

docs(changelog): elevate the project-scoping section

Retitle "Constraint: one OAuth app, one project" to the more attention-grabbing "Heads up: OAuth apps are project-scoped on V2" and lead the section with an action-required callout instead of schema jargon. Drop the internal uniqueness-index sentence; keep the customer-facing rule and rationale. _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 18, 2026 at 21:44 UTC 373b050d0fe8ebcf7b2014654a0add2aaa4df08e
1 file changed +9 -9
docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+9 -9
@@ -128,23 +128,23 @@ curl -X POST "https://backend.composio.dev/api/v3/trigger_instances/SLACK_CHANNE
128
129 Creating a V2-only slug without a matching `webhook_endpoint` returns `400` with a `suggestedFix` pointing to `POST /api/v3/webhook_endpoints`.
130
131 -## Constraint: one OAuth app, one project
132 -
133 -`webhook_endpoints` uniqueness is `(toolkit_slug, project_id, client_id)`. More importantly, the provider dashboard accepts exactly **one callback URL per OAuth app**, and each V2 URL resolves to a single project.
131 +## Heads up: OAuth apps are project-scoped on V2
132
133 <Callout type="warn">
136 -An OAuth app (`client_id`) on V2 can effectively serve only one Composio project. If the same OAuth app is currently shared across multiple projects or organizations on V1, either pick one project to own it on V2 or register separate OAuth apps per project.
134 +**Action required if you share a single OAuth app across multiple Composio projects or organizations today.** V2 ties each OAuth app (`client_id`) to exactly one project. Before moving such an app to V2, either consolidate to a single project or register separate OAuth apps per project.
135 </Callout>
136
139 -Scoping V2 endpoints to a single project gives each project:
137 +The provider dashboard accepts only one callback URL per OAuth app, and each V2 URL resolves to exactly one project — so a single OAuth app cannot feed multiple projects on V2.
138 +
139 +Project-scoped endpoints give each project:
140
141 -- Its own ingress rate-limit and backpressure budget
142 -- Isolated fan-out — events reach only that project's trigger instances
143 -- Isolated signing secret and app-level token storage
141 +- A dedicated ingress rate-limit and backpressure budget
142 +- Clean fan-out — events reach only that project's trigger instances
143 +- A signing secret and app-level token scoped to this project alone
144 - Accurate per-project metering and billing
145 - Independent teardown, rotation, and verification state
146
147 -V1's shared endpoint continues to work for any OAuth app left on V1, with no change in behavior.
147 +Your V1 endpoints are unaffected. Any OAuth app you leave on V1 continues to work across projects exactly as it does today.
148
149 ## Backward compatibility
150