@devries-cameron20 / composio Mirror · read-only / commits / 257ad9d24
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): fix payload/cURL examples — valid event_id, PATCH, consistent placeholders, v3

- Replace invalid event_id placeholder msg_abc123 with a valid 36-char UUID-format value that matches EventIdSchema /^msg_[0-9a-f-]{36}$/ — otherwise the docs example fails our own regex. - Switch the API cURL from POST (creates a new subscription) to PATCH an existing subscription's enabled_events. Matches the stated intent ("Add this event to your subscription"); avoids accidentally creating a second subscription and duplicating deliveries. - Standardize placeholder style: pr_your-project-id, ti_your-trigger-id, ca_your-connected-account-id, ws_your-subscription-id, your-user-id. Same convention as 02-06-26-webhook-subscriptions-api.mdx. - Name both endpoints symmetrically in the "does not fire when" line: PATCH /api/v3/trigger_instances/manage/{id} and PATCH /api/v3/connected_accounts/{id}/status. - Add a trailing clarification on trigger_config: its fields vary per trigger type, and the example shows GitHub's owner/repo. - Use v3 consistently across cURL and prose (no v3.1 drift). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 23, 2026 at 19:17 UTC 257ad9d24d23763897e0751d282ca93c9386add1
1 file changed +8 -9
docs/content/changelog/04-23-26-trigger-disabled-event.mdx
+8 -9
@@ -17,20 +17,19 @@ The event is emitted only for platform-initiated disables. `data.disabled_reason
17 | `subscription_refresh_failure` | Composio could not reach the provider to refresh the webhook subscription (provider error, timeout, or network issue). Re-enable the trigger once the provider is healthy. |
18 | `polling_failure_in_composio_infra` | A polling trigger was reported unhealthy by Composio's polling infrastructure. Rare in practice, and the reliability of our polling stack continues to improve. |
19
20 -The event does not fire when you disable a trigger yourself — neither through the trigger instance manage endpoint nor by deactivating the connected account with `PATCH /api/v3/connected_accounts/{nanoid}/status`.
20 +The event does not fire when you disable a trigger yourself — neither through `PATCH /api/v3/trigger_instances/manage/{id}` nor by deactivating the connected account via `PATCH /api/v3/connected_accounts/{id}/status`.
21
22 ## Subscribe
23
24 Add `composio.trigger.disabled` from the [dashboard webhook settings](https://platform.composio.dev?next_page=/settings/webhook) — the fastest path for most teams. Select the event in the **Events** list and save.
25
26 -Or via the Webhook Subscriptions API:
26 +Or via the Webhook Subscriptions API — PATCH an existing subscription's `enabled_events`:
27
28 ```bash
29 -curl -X POST https://backend.composio.dev/api/v3.1/webhook_subscriptions \
29 +curl -X PATCH https://backend.composio.dev/api/v3/webhook_subscriptions/ws_your-subscription-id \
30 -H "X-API-KEY: <your-composio-api-key>" \
31 -H "Content-Type: application/json" \
32 -d '{
33 - "webhook_url": "https://example.com/webhook",
33 "enabled_events": [
34 "composio.trigger.message",
35 "composio.trigger.disabled"
@@ -44,16 +43,16 @@ The event is V3-only. Subscriptions on V1 or V2 payloads cannot enable it.
43
44 ```json
45 {
47 - "id": "msg_abc123",
46 + "id": "msg_847cdfcd-d219-4f18-a6dd-91acd42ca94a",
47 "type": "composio.trigger.disabled",
48 "metadata": {
49 "project_id": "pr_your-project-id"
50 },
51 "data": {
53 - "id": "ti_xyz789",
54 - "connected_account_id": "ca_def456",
52 + "id": "ti_your-trigger-id",
53 + "connected_account_id": "ca_your-connected-account-id",
54 "trigger_name": "GITHUB_COMMIT_EVENT",
56 - "user_id": "user-id-12345",
55 + "user_id": "your-user-id",
56 "trigger_config": { "owner": "composio", "repo": "hermes" },
57 "disabled_at": "2026-04-23T11:59:59.000Z",
58 "disabled_reason": "connection_expired"
@@ -62,6 +61,6 @@ The event is V3-only. Subscriptions on V1 or V2 payloads cannot enable it.
61 }
62 ```
63
65 -`user_id` is `null` on triggers from toolkits that do not require authentication.
64 +`user_id` is `null` on triggers from toolkits that do not require authentication. `trigger_config` holds the configuration you passed when creating the trigger — its fields vary per trigger type (the example above shows GitHub's `owner` / `repo`).
65
66 See [subscribing to triggers](/docs/setting-up-triggers/subscribing-to-events) for handler setup and [subscribing to connection expiry events](/docs/subscribing-to-connection-expiry-events) for re-auth flows on `connection_expired`.