@devries-cameron20 / composio-1 / commits / bd2a2551c
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): elevate the project-scoped benefits lead-in

Replace the bureaucratic "Project-scoped endpoints give each project:" with a confident value framing — every project graduates to a first-class webhook tenant on V2. Tighten the bullets to start with the noun (rate-limit, fan-out, signing secret, metering) and let the "with its own" lead-in carry the possessive. _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 18, 2026 at 22:16 UTC bd2a2551cec5ca6b61031fdfb04339e17baee494
1 file changed +4 -4
docs/content/changelog/04-20-26-webhook-triggers-v2.mdx
+4 -4
@@ -138,12 +138,12 @@ The provider dashboard accepts only one callback URL per OAuth app, and each V2
138
139 The signing secret also lives on the endpoint, so the reverse holds too: two different OAuth apps cannot share one V2 endpoint — Composio would only verify signatures from the app whose secret is on file.
140
141 -Project-scoped endpoints give each project:
141 +In return, every project graduates to a first-class webhook tenant on V2 — with its own:
142
143 -- A dedicated ingress rate-limit and backpressure budget
143 +- Ingress rate-limit and backpressure budget
144 - Clean fan-out — events reach only that project's trigger instances
145 -- A signing secret and app-level token scoped to this project alone
146 -- Accurate per-project metering and billing
145 +- Signing secret and app-level token, scoped to this project alone
146 +- Per-project metering and billing
147
148 Your V1 endpoints are unaffected. Any OAuth app you leave on V1 continues to work across projects exactly as it does today.
149