Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs(changelog): reframe per-user authz as a capability, not a V1 fix
Anshu Garg02343a550b88
diff --git a/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx b/docs/content/changelog/04-18-26-webhook-triggers-v2.mdxindex ec20efb1a..15da51f66 100644--- a/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx+++ b/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx@@ -28,7 +28,7 @@ This replaces V1's shared `/handle` URL per toolkit. Events arriving on a V2 URL**Signature verification at ingress.** Apollo cryptographically verifies every V2 request against the signing secret stored on the endpoint — HMAC-SHA256, Ed25519, or `token_match` depending on the toolkit. Unsigned or tampered payloads are rejected, so third parties cannot spoof events onto your triggers. For providers that sign a request timestamp (e.g. Slack), replay protection additionally rejects requests whose timestamp falls outside the allowed skew window.-**Per-user authorization for app-level events.** Toolkits with per-user visibility — Slack being the first — can use an app-level token (e.g. `xapp-…` with `authorizations:read`) to resolve which connected users are authorized for a given event. Only those users' triggers fire. This enables safe delivery of private channel and DM events that V1 silently dropped.+**Per-user authorization for app-level events.** On toolkits with per-user visibility — Slack being the first — V2 uses an app-level token (for Slack, an `xapp-…` token with `authorizations:read`) to resolve which connected users are authorized for a given event, so only those users' triggers fire. This underpins a new class of triggers for private channels, direct messages, and other per-recipient events, each routed only to the user the event was intended for.**Config-level filters.** V2 triggers filter events against `trigger_config` at match time: