@devries-cameron20 / composio Mirror · read-only / commits / ddf60064a
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): rename to 04-24, add schema sample response, clarify secret-on-endpoint wording

- Rename 04-20-26 → 04-24-26 to match the actual release date, update frontmatter date and the example created_at timestamp accordingly. - Add a sample response body to the "Discover required fields" step so customers see the shape of webhook_endpoints/schema output (setup fields, description, is_secret flags) without having to run it. - Replace "secret is on file" phrasing, which leaks internal storage terminology, with "secret stored on that endpoint" so customers reason about endpoints, not files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 24, 2026 at 03:10 UTC ddf60064aed7565a051e0344bfcf6caa0d6b3c62
1 file changed +25 -3
docs/content/changelog/04-24-26-webhook-triggers-v2.mdx renamed
+25 -3
@@ -1,7 +1,7 @@
1 ---
2 title: "Webhook Triggers V2"
3 description: "Dedicated webhook endpoint per OAuth app, ingress-level signature verification, per-user authorization for private channels and DMs, and config-level event filters. Opt-in; V1 is unchanged."
4 -date: "2026-04-20"
4 +date: "2026-04-24"
5 ---
6
7 Webhook Triggers V2 introduces a first-class `webhook_endpoints` resource with a dedicated ingress URL per OAuth app. V2 is **opt-in** and scoped to new trigger slugs — existing V1 triggers, URLs, and payload formats are unchanged.
@@ -62,6 +62,28 @@ curl "https://backend.composio.dev/api/v3/webhook_endpoints/schema?toolkit_slug=
62 -H "x-api-key: YOUR_API_KEY"
63 ```
64
65 +Sample response:
66 +
67 +```json
68 +{
69 + "toolkit_slug": "slack",
70 + "setup_fields": {
71 + "webhook_signing_secret": {
72 + "display_name": "Signing Secret",
73 + "description": "Webhook request signing secret from your Slack app dashboard",
74 + "is_required": true,
75 + "is_secret": true
76 + },
77 + "app_token": {
78 + "display_name": "App-Level Token",
79 + "description": "Slack xapp- token with authorizations:read scope for event authorization",
80 + "is_required": true,
81 + "is_secret": true
82 + }
83 + }
84 +}
85 +```
86 +
87 ### 2. Create the endpoint
88
89 ```bash
@@ -80,7 +102,7 @@ Sample response:
102 "client_id": "YOUR_SLACK_CLIENT_ID",
103 "webhook_url": "https://backend.composio.dev/api/v3/webhook_ingress/slack/we_abc123/trigger_event",
104 "data": null,
83 - "created_at": "2026-04-20T10:00:00.000Z"
105 + "created_at": "2026-04-24T10:00:00.000Z"
106 }
107 ```
108
@@ -148,7 +170,7 @@ curl -X POST "https://backend.composio.dev/api/v3/trigger_instances/SLACK_CHANNE
170
171 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.
172
151 -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.
173 +The signing secret also lives on the endpoint, so the reverse holds too: two different OAuth apps cannot share one V2 endpoint — Composio only verifies signatures against the secret stored on that endpoint, so requests signed by a different OAuth app would be rejected.
174
175 In return, every project graduates to a first-class webhook tenant on V2 — with its own:
176