connector.* events

A project's connectors as they are installed, connected, verified, configured and disconnected: the family every connector answers to.

A project's connectors as they are installed, connected, verified, configured and disconnected: the family every connector answers to.

A project runs on connectors: the platforms it gates access on, sends messages through and takes payments from. Each one the project runs is an installation, and every move in an installation's life is announced here: it is installed (a pending row, no credentials yet), connected (the creator handed the connector its credentials), verified or probed (its state moved), configured (a declared setting changed), disconnected (the credentials wiped, the row kept) and uninstalled (its grants revoked and resources detached, the row still kept). The events name Subscriby ids and the connector key only; a platform's own identifiers, tokens and settings values never travel in a webhook.

EventFires when
connector.installedA connector was installed on a project: a pending installation, no credentials yet.
connector.connectedThe creator connected the installation with their credentials; it can act now.
connector.status_changedA probe or a verify moved the installation's state.
connector.outage_openedThe platform refused the live installation outright; plans that unlock a place on it are off sale.
connector.outage_closedThe outage ended: recovered, replaced or uninstalled, with how long it ran.
connector.outage_compensatedThe outage settled: how many members had its length banked on their purchase, and how many lost invites were re-sent.
connector.doctor_completedThe connector doctor ran and found something different from last time.
connector.settings_updatedA declared setting of the installation changed; which ones, never the values.
connector.disconnectedThe installation was disconnected: credentials wiped, row kept, members untouched.
connector.uninstalledThe connector was uninstalled: grants revoked, resources detached, the row kept; with the counts.

Read them together with the API

The installation_id in every payload is the id of the rows the project's installations endpoint lists, and connector is the key of a card in the connector directory. A consumer that keeps a mirror of a project's connectors applies these events to those rows.

Example envelope

{
  "id": "evt_01HX...",
  "type": "connector.connected",
  "created_at": "2026-09-12T10:06: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",
    "display_name": "Research Bot",
    "handle": "research_bot"
  }
}

Required ability

Every connector.* event requires project-connector:view on the subscribing token and carries the project's project_id.

Events

Compare with the current pages

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