@devries-cameron20 / composio-1 / commits / 96db44636
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): decouple match-time filters from V2 framing

Config-level filters aren't exclusive to V2 — they're a parallel capability rolling out alongside it. Rename the heading, lead with the Slack example, and signal that more toolkits will expose similar filters over time. _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 18, 2026 at 21:39 UTC 96db446362cbfcfeb6eb30e5cf1044f2d17eec2d
1 file changed +3 -1
docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+3 -1
@@ -30,7 +30,7 @@ This replaces V1's shared `/handle` URL per toolkit. Events arriving on a V2 URL
30
31 **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.
32
33 -**Config-level filters.** V2 triggers filter events against `trigger_config` at match time:
33 +**Match-time filters on new triggers.** Alongside V2, triggers are gaining optional match-time filters set via `trigger_config`. `SLACK_CHANNEL_MESSAGE_RECEIVED`, for example, accepts `channel_id`, `is_bot_message`, and `is_thread_reply`, and only delivers events matching the filter:
34
35 ```json
36 {
@@ -42,6 +42,8 @@ This replaces V1's shared `/handle` URL per toolkit. Events arriving on a V2 URL
42 }
43 ```
44
45 +More toolkits will expose similar filters as they roll out.
46 +
47 **Lifecycle support.** Provider handshakes (Slack `url_verification`, Asana `X-Hook-Secret`, Outlook validation tokens) are handled at ingress. Provider-side webhooks are deregistered when user-level triggers are deleted.
48
49 ## API reference