connector.* events
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.
Every connector.* event requires project-connector:view on the subscribing token and carries the project's project_id.
Events
connector.installed
A connector was installed on a project: a pending installation, no credentials yet.
connector.connected
The creator connected the installation with their credentials; it can act now.
connector.status_changed
A probe or a verify moved the installation's state.
connector.outage_opened
The platform refused the live installation outright; plans that unlock a place on it are off sale.
connector.outage_closed
The outage ended: recovered, replaced or uninstalled, with how long it ran.
connector.outage_compensated
The outage settled: how many members had its length banked on their purchase, and how many lost invites were re-sent.
connector.doctor_completed
The connector doctor ran and found something different from last time.
connector.settings_updated
A declared setting of the installation changed; which ones, never the values.
connector.disconnected
The installation was disconnected: credentials wiped, row kept, members untouched.
connector.uninstalled
The 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 GET /v1/projects/{project}/connectors lists, and connector is the key of a card in GET /v1/connectors. A consumer that keeps a mirror of a project's connectors applies these events to those rows.
How is this guide?