@devries-cameron20 / composio Mirror · read-only / commits / e19792c0a
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, 21:00 UTC

docs(creating-triggers): convert upsides + signature verification to bullets

The two prose paragraphs about per-tenant guarantees and ingress signature checks were dense walls of text. Restructure as bullets matching the V2 announcement changelog's format. Each item now stands on its own line, scannable. Word-level edits: - "since providers accept" → "providers accept" (drop redundant conjunction; colon does the work) - "The upside:" → "In return," — acknowledges it's a trade - "every project becomes its own webhook tenant with isolated..." → restructured as a lead-in followed by 4 bullets - "Provider events are verified at ingress against the endpoint's signing secret before any trigger fires —" → "Every inbound event is signature-checked at ingress before any trigger fires:" — active, shorter - Replay protection bullet is no longer a "for providers..." parenthetical; it's its own item Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed May 7, 2026 at 21:01 UTC e19792c0a9846043c3083103beeb985cd9e0676e
1 file changed +11 -2
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+11 -2
@@ -96,9 +96,18 @@ Each OAuth app you bring gets its own ingress URL within a project:
96 https://backend.composio.dev/api/v3.1/webhook_ingress/{toolkit_slug}/{we_xxx}/trigger_event
97 ```
98
99 -A single OAuth app can serve at most one Composio project, since providers accept only one callback URL per OAuth app and each ingress URL routes to a single project. The upside: every project becomes its own webhook tenant with isolated ingress rate limits, its own signing secret and app-level token, clean fan-out (events only reach that project's triggers), and per-project metering. Repeat verification handshakes are rejected after the endpoint is verified, so the signing secret can't be silently swapped.
99 +A single OAuth app can serve at most one Composio project: providers accept only one callback URL per OAuth app, and each ingress URL routes to a single project. In return, every project becomes its own webhook tenant — with:
100
101 -Provider events are verified at ingress against the endpoint's signing secret before any trigger fires — HMAC-SHA256 for Slack, Ed25519 or shared-token matching for others. For providers that sign a request timestamp, replay protection additionally rejects requests outside the allowed skew window. Unsigned or tampered requests get a `400` at ingress, so third parties cannot spoof events onto your triggers.
101 +- **Its own ingress rate limit and backpressure budget**
102 +- **Its own signing secret and app-level token**, scoped to this project alone. Repeat verification handshakes are rejected after the endpoint is verified, so the signing secret can't be silently swapped by a forged challenge.
103 +- **Clean fan-out** — events reach only that project's trigger instances
104 +- **Per-project metering**
105 +
106 +Every inbound event is signature-checked at ingress before any trigger fires:
107 +
108 +- **HMAC-SHA256** for Slack, **Ed25519** or shared-token matching for other providers
109 +- **Timestamp replay protection** — when the provider signs a request timestamp, requests outside the allowed skew window are rejected
110 +- **Unsigned or tampered requests** are rejected with `400` at ingress, so third parties can't spoof events onto your triggers
111
112 <Callout type="warn">
113 **Sharing one OAuth app across projects?** Consolidate to a single project or register separate OAuth apps per project before continuing.