@devries-cameron20 / composio Mirror · read-only / commits / 4509e31ed
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): address Rahul's review feedback

- Move file + frontmatter date to 2026-04-23 (ship date). - Add a rarity/reliability note to the `polling_failure_in_composio_infra` row so the wording isn't just "we had a problem." - Lead the Subscribe section with the dashboard UI path — the most common flow — and keep the cURL as the API alternative. - Strengthen the "when not fired" copy in the events table on the "Subscribing to triggers" docs page (bold fired / not fired, explicit manage-API + connected-account deactivation paths). - Drop `version`, `updated_at`, and `metadata.org_id` from the payload JSON example to match the shipped event shape (hermes PR updated the payload after this changelog was first written). - Refresh example timestamps to 2026-04-23. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 23, 2026 at 19:13 UTC 4509e31edb6ac9e7b7dd4612b59e50157a07edce
2 files changed +10 -11
docs/content/changelog/04-23-26-trigger-disabled-event.mdx renamed
+9 -10
@@ -1,7 +1,7 @@
1 ---
2 title: "Webhook Event for Auto-Disabled Triggers"
3 description: "New composio.trigger.disabled event fires when Composio disables a trigger on your behalf — expired connection, webhook refresh failure, or unhealthy polling. Opt-in, V3-only."
4 -date: "2026-04-22"
4 +date: "2026-04-23"
5 ---
6
7 `composio.trigger.disabled` is a new V3 webhook event that fires when Composio disables one of your triggers without a request from you — expired credentials, a failed webhook-subscription refresh, or unhealthy polling. It's opt-in: add it to a webhook subscription's `enabled_events` to receive it. Existing subscriptions for `composio.trigger.message` and `composio.connected_account.expired` are unaffected.
@@ -15,13 +15,15 @@ The event is emitted only for platform-initiated disables. `data.disabled_reason
15 | `connection_expired` | The connected account entered `EXPIRED` and the trigger was paused. Auto-re-enabled when the account returns to `ACTIVE`. |
16 | `subscription_auth_failure` | The provider rejected the credentials when Composio tried to refresh the webhook subscription. Re-auth the connection to resolve. |
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. |
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`.
21
22 ## Subscribe
23
24 -Add `composio.trigger.disabled` to your subscription's `enabled_events`:
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:
27
28 ```bash
29 curl -X POST https://backend.composio.dev/api/v3.1/webhook_subscriptions \
@@ -45,24 +47,21 @@ The event is V3-only. Subscriptions on V1 or V2 payloads cannot enable it.
47 "id": "msg_abc123",
48 "type": "composio.trigger.disabled",
49 "metadata": {
48 - "project_id": "pr_your-project-id",
49 - "org_id": "your-org-id"
50 + "project_id": "pr_your-project-id"
51 },
52 "data": {
53 "id": "ti_xyz789",
54 "connected_account_id": "ca_def456",
55 "trigger_name": "GITHUB_COMMIT_EVENT",
56 "user_id": "user-id-12345",
56 - "version": "20260315_00",
57 "trigger_config": { "owner": "composio", "repo": "hermes" },
58 - "updated_at": "2026-04-22T11:59:59.000Z",
59 - "disabled_at": "2026-04-22T11:59:59.000Z",
58 + "disabled_at": "2026-04-23T11:59:59.000Z",
59 "disabled_reason": "connection_expired"
60 },
62 - "timestamp": "2026-04-22T12:00:00.000Z"
61 + "timestamp": "2026-04-23T12:00:00.000Z"
62 }
63 ```
64
66 -`user_id` is `null` on triggers from toolkits that do not require authentication. The `data` object mirrors the non-deprecated fields returned per item by `GET /api/v3/trigger_instances/active`, plus `disabled_reason`.
65 +`user_id` is `null` on triggers from toolkits that do not require authentication.
66
67 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`.
docs/content/docs/setting-up-triggers/subscribing-to-events.mdx
+1 -1
@@ -12,7 +12,7 @@ Webhooks are the recommended way to receive trigger events in production. To sta
12 |------------|-------------|
13 | `composio.trigger.message` | Fired when a trigger receives data from an external service. |
14 | `composio.connected_account.expired` | Fired when a connected account expires and needs re-authentication. See [Subscribing to connection expiry events](/docs/subscribing-to-connection-expiry-events). |
15 -| `composio.trigger.disabled` | Fired when Composio automatically disables a trigger (expired connection, webhook refresh failure, or unhealthy polling). Not fired when you disable a trigger or its connected account yourself. |
15 +| `composio.trigger.disabled` | **Fired when** Composio automatically disables a trigger — expired connection, webhook refresh failure, or unhealthy polling. **Not fired when** you disable a trigger through the manage API or deactivate its connected account via `PATCH /api/v3/connected_accounts/{id}/status`. See the [changelog entry](/docs/changelog/2026/04/23) for the full list of `disabled_reason` values. |
16
17 Set your webhook URL in the [dashboard settings](https://platform.composio.dev?next_page=/settings/webhook) or via the [Webhook Subscriptions API](/reference/api-reference/webhooks):
18