Documentation
Version
Platform Dashboard GuideREST API ReferenceMCP Server for AI AgentsBuilding ConnectorsWebhooks & EventsAutomations & Integrations
WRITE

run_connector_doctor

Verify a project's installation of a connector and ask the connector about every resource it gates — one report, a finding per check.

The dashboard's Run Doctor for agents. The installation is verified exactly as verify_connector_installation does it, then the connector is asked about every resource the installation gates, and the answer is one report: a finding for the installation, then one per resource, each with a severity (ok, warning, critical), the connector's own state word, a sentence in the creator's language, whether the creator can fix it and where. A resource the connector has no place for is a warning, never silence. The report is kept on the installation and raises connector.doctor_completed only when the findings differ from the previous run's. The REST twin is POST /v1/projects/{project}/connectors/{key}/installation/doctor.

Requires ability

project-connector:update

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

POST/v1/projects/{project}/connectors/{key}/installation/doctor

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Fires one event

connector.doctor_completed

Delivered to every endpoint subscribed to it once the change is made.

Annotations

Idempotent

Sending the same arguments twice changes nothing the second time.

Arguments

project_id*string

UUID of the project.

connector*string

The connector key, as `list_connectors` returns it.

What it returns

{  "data": {    "installation_id": "3b8f0c6e-2d41-4a97-9e5f-1c7d6b2a8e40",    "connector": "telegram",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "ran_at": "2026-09-12T10:07:00Z",    "healthy": false,    "critical": 1,    "warnings": 0,    "findings": [      {        "key": "installation",        "kind": "installation",        "severity": "ok",        "severity_label": "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",        "severity_label": "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"      }    ]  },  "meta": {}}

How it fails

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks project-connector:update.

RESOURCE_NOT_FOUND

the project is unknown or outside the token's reach.

CONNECTOR_NOT_INSTALLED

the project has no installation of the connector.

Related

verify_connector_installationthe installation alone.get_connector_installationthe installation with doctor_ran_at and doctor_healthy.connector.doctor_completedConnectors API

How is this guide?

Last updated on

restore_connector_access

Bring a project's detached places on a reinstalled connector back and hand every live purchase of a plan granting them fresh access.

uninstall_connector

Uninstall a connector from a project — grants revoked, resources detached, the row kept — with two opt-ins for the plans it empties. Destructive.