13
| `disabled_reason` | What it means |
14
|---|---|
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` | Composio tried to refresh the provider-side webhook subscription and the provider rejected the credential. |
17
-| `subscription_refresh_failure` | Composio tried to refresh the provider-side webhook subscription and retries ran out. |
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. |
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`.
65
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`.
67
68
-## Handling
69
-
70
-Route on `type` alongside your existing handlers:
71
-
72
-```typescript
73
-type NextApiRequest = { body: any };
74
-type NextApiResponse = { status: (code: number) => { json: (data: any) => void } };
75
-// ---cut---
76
-export default async function webhookHandler(req: NextApiRequest, res: NextApiResponse) {
77
- const payload = req.body;
78
-
79
- if (payload.type === 'composio.trigger.disabled') {
80
- const { id, connected_account_id, trigger_name, disabled_reason } = payload.data;
81
-
82
- if (disabled_reason === 'connection_expired') {
83
- // Prompt the user to re-authenticate; the trigger re-enables on its own.
84
- } else {
85
- // subscription_auth_failure, subscription_refresh_failure, polling_failure_in_composio_infra
86
- // These do not auto-re-enable — inspect the trigger and re-enable once resolved.
87
- }
88
- }
89
-
90
- res.status(200).json({ status: 'ok' });
91
-}
92
-```
93
-
94
-For general webhook setup, see [subscribing to triggers](/docs/setting-up-triggers/subscribing-to-events); for re-auth flows on connection expiry, see [subscribing to connection expiry events](/docs/subscribing-to-connection-expiry-events).
68
+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`.