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): address Rahul's review feedback
Anshu Garg4509e31edb6a
diff --git a/docs/content/changelog/04-22-26-trigger-disabled-event.mdx b/docs/content/changelog/04-23-26-trigger-disabled-event.mdxsimilarity index 83%rename from docs/content/changelog/04-22-26-trigger-disabled-event.mdxrename to docs/content/changelog/04-23-26-trigger-disabled-event.mdxindex 5c01252b2..b19f41f99 100644--- a/docs/content/changelog/04-22-26-trigger-disabled-event.mdx+++ b/docs/content/changelog/04-23-26-trigger-disabled-event.mdx@@ -1,7 +1,7 @@---title: "Webhook Event for Auto-Disabled Triggers"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."-date: "2026-04-22"+date: "2026-04-23"---`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| `connection_expired` | The connected account entered `EXPIRED` and the trigger was paused. Auto-re-enabled when the account returns to `ACTIVE`. || `subscription_auth_failure` | The provider rejected the credentials when Composio tried to refresh the webhook subscription. Re-auth the connection to resolve. || `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. |-| `polling_failure_in_composio_infra` | A polling trigger was reported unhealthy by Composio's polling infrastructure. |+| `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. |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`.## Subscribe-Add `composio.trigger.disabled` to your subscription's `enabled_events`:+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.++Or via the Webhook Subscriptions API:```bashcurl -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."id": "msg_abc123","type": "composio.trigger.disabled","metadata": {- "project_id": "pr_your-project-id",- "org_id": "your-org-id"+ "project_id": "pr_your-project-id"},"data": {"id": "ti_xyz789","connected_account_id": "ca_def456","trigger_name": "GITHUB_COMMIT_EVENT","user_id": "user-id-12345",- "version": "20260315_00","trigger_config": { "owner": "composio", "repo": "hermes" },- "updated_at": "2026-04-22T11:59:59.000Z",- "disabled_at": "2026-04-22T11:59:59.000Z",+ "disabled_at": "2026-04-23T11:59:59.000Z","disabled_reason": "connection_expired"},- "timestamp": "2026-04-22T12:00:00.000Z"+ "timestamp": "2026-04-23T12:00:00.000Z"}```-`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`.+`user_id` is `null` on triggers from toolkits that do not require authentication.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`.diff --git a/docs/content/docs/setting-up-triggers/subscribing-to-events.mdx b/docs/content/docs/setting-up-triggers/subscribing-to-events.mdxindex d2f3c23df..aefc6f6a7 100644--- a/docs/content/docs/setting-up-triggers/subscribing-to-events.mdx+++ b/docs/content/docs/setting-up-triggers/subscribing-to-events.mdx@@ -12,7 +12,7 @@ Webhooks are the recommended way to receive trigger events in production. To sta|------------|-------------|| `composio.trigger.message` | Fired when a trigger receives data from an external service. || `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). |-| `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. |+| `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. |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):