An installation was disconnected: the connector withdrew it, the credentials were wiped, the row stays.
When this fires
A creator disconnects an installation, from the Connectors tab, through the disconnect endpoint or the disconnect_connector tool. The connector withdraws the installation on its platform, the credentials are wiped and the installation turns disconnected; grants, resources, plans and identities are untouched and members keep the access they hold. Disconnecting an installation already disconnected fires nothing.
Caveats
- Disconnecting is not uninstalling: nothing is revoked and no plan is touched. Uninstalling, with its impact preview, is a separate act and fires connector.uninstalled.
Related events
- connector.connected: the reverse.
- connector.status_changed: a platform-side revocation, as opposed to the creator's own disconnect.
Headers
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.