connector.disconnected

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 DELETE …/installation 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.

Required ability

project-connector:view — token must carry this at mint time to subscribe an endpoint to this event.

Payload

{
  "id": "evt_01HX...",
  "type": "connector.disconnected",
  "created_at": "2026-09-12T11:00:00Z",
  "api_version": "2026-05-01",
  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
  "data": {
    "connector": "telegram",
    "installation_id": "3b8f0c6e-2d41-4a97-9e5f-1c7d6b2a8e40",
    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13"
  }
}

Field reference

FieldTypeNotes
idstring ULIDUnique event id, prefixed evt_. Use for idempotent processing.
typestringAlways connector.disconnected for this event.
created_atISO 8601 timestampServer-side emission time.
api_versionstringWebhook API contract version.
project_idstring UUIDProject this event belongs to.
data.connectorstringThe connector key.
data.installation_idstring UUIDThe installation row, which stays and can be connected again.
data.project_idstring UUIDMirrors top-level project_id.

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.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request