connector.connected

The creator connected an installation with their credentials; the connector can act for the project now.

When this fires

A creator completes a connector's connect flow on the dashboard: the connector checks the credentials, registers with its platform and the installation turns connected. For the first connector this is the Connect Bot modal, the platform bot's connectivity conversation and a Disaster Recovery bot replacement.

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.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"
  }
}

Field reference

FieldTypeNotes
idstring ULIDUnique event id, prefixed evt_. Use for idempotent processing.
typestringAlways connector.connected 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.
data.project_idstring UUIDMirrors top-level project_id.
data.display_namestring | nullThe platform's display name for the installation (the bot's name).
data.handlestring | nullThe platform's handle for the installation (the bot's username), without a leading @.

Caveats

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