project.bot.connected

When this fires

A creator completes the bot-connectivity flow and a Telegram bot is bound to the project. The bot starts responding to subscriber messages immediately after this event.

Required ability

project:view-any — token must carry this at mint time to subscribe an endpoint to this event.

Payload

{
  "id": "evt_01HX...",
  "type": "project.bot.connected",
  "created_at": "2026-05-18T10:05:00Z",
  "api_version": "2026-05-01",
  "project_id": "prj_01HX...",
  "data": {
    "project_id": "prj_01HX...",
    "bot_id": "bot_01HX...",
    "bot_name": "ResearchPremiumBot",
    "bot_url": "https://t.me/ResearchPremiumBot"
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `project.bot.connected` for this event.
`created_at`	ISO 8601 timestamp	Server-side emission time.
`api_version`	string	Webhook API contract version.
`project_id`	string ULID	Project this event belongs to.
`data.project_id`	string ULID	Mirrors top-level `project_id`.
`data.bot_id`	string ULID	bot identifier.
`data.bot_name`	string	Telegram bot username (without `@`).
`data.bot_url`	string	Public `t.me/..` URL for the bot.

Caveats

Bot tokens are never included in the payload. Use the bot_id for any cross-reference back to the dashboard.
Rotating a bot fires project.bot.disconnected followed by project.bot.connected for the new bot.

project.bot.disconnected — paired transition.
project.bot.status_changed — health monitoring (deferred).
Project events overview — back to family overview.