connector.doctor_completed

The connector doctor ran on an installation and found something different from the previous run.

When this fires

The creator pressed Run Doctor on the Connectors tab or the connector's page, an integration called the doctor endpoint or run_connector_doctor, or the platform's scheduled sweep ran, and the report differs from the one kept on the installation: a finding appeared, disappeared or changed severity or state. A run that finds exactly what the last one found fires nothing, so a nightly sweep is quiet until something moves. The installation's own verification inside the run still fires connector.status_changed when the state moved.

Caveats

The first run on an installation fires this event, because there is no earlier report to match; a repeat with the same findings does not.
A resource the connector has no place it can ask about (no space row, no legacy chat) is a warning finding, never left out.
Sentences are rendered in the creator's language at the time of the run; the state words are stable.

Related events

connector.status_changed: the installation's own verdict, fired by the verification inside the run when the state moved.

Ability to subscribe

project-connector:view

A token needs this to subscribe an endpoint to the event.

Header Parameters

SB-Signature*string

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=.

SB-Event-Id*string

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.

SB-Event-Name*string

The event name, the same as the envelope's type.

Content-Type*string

Always application/json.

User-Agent*string

Always Subscriby-Webhooks/1.0.

Payload

JSONWhat Subscriby posts to your endpointapplication/json

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

id*string

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type*"connector.doctor_completed"

The event name, always connector.doctor_completed here.

Value in

"connector.doctor_completed"

created_at*string

When the event was emitted, server time, ISO 8601.

Formatdate-time

api_version*string

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_id*|

The project the event belongs to; null for team-scoped and billing events.

Formatuuid

data*

The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.

Responses

2XXAny success status

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

defaultAny other status

Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.

Delivery to your endpoint

Subscriby sends this event as one HTTP request to every endpoint subscribed to it.

POSThttps://example.com/webhooks/subscribyyour endpoint URL

Headers

SB-Signature: t=1758636300,v1=5f1c…
SB-Event-Id: 01HXDELIVERY000000000TST
SB-Event-Name: connector.doctor_completed
Content-Type: application/json
User-Agent: Subscriby-Webhooks/1.0

Body

{  "id": "evt_01HX...",  "type": "connector.doctor_completed",  "created_at": "2026-09-12T10:07: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",    "ran_at": "2026-09-12T10:07:00+00:00",    "healthy": false,    "critical": 1,    "warnings": 0,    "findings": [      {        "key": "installation",        "kind": "installation",        "severity": "ok",        "subject": "Research Bot",        "state": "connected",        "message": "The connector still answers for this installation.",        "creator_actionable": false,        "fix_url": null,        "resource_id": null      },      {        "key": "resource:b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",        "kind": "resource",        "severity": "critical",        "subject": "Premium Channel",        "state": "not_member",        "message": "The bot was removed from this channel.",        "creator_actionable": true,        "fix_url": "https://app.subscriby.net/projects/7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13/resources",        "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6"      }    ]  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Body {  id: string;  type: "connector.doctor_completed";  created_at: string;  api_version: string;  project_id: string | null;  data: Data;}export interface Data {  connector: string;  installation_id: string;  project_id: string;  ran_at: string;  healthy: boolean;  critical: number;  warnings: number;  findings: Finding[];}export interface Finding {  key: string;  kind: "installation" | "resource";  severity: "ok" | "warning" | "critical";  subject: string;  state: string;  message: string;  creator_actionable: boolean;  fix_url: string | null;  resource_id: string | null;}

When it arrives

Verify the signatureCheck the SB-Signature header before trusting anything in the body.Answer 2xx within 30 secondsAny other answer, or none, and Subscriby retries the delivery.

De-duplicate on SB-Event-IdA retry carries the same id as the first attempt.