project.resource.linked

When this fires

A creator links a Telegram channel, group, or supergroup from inside the bot's RequestChat flow. This creates the resource row — no project.resource.created precedes it.

Required ability

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

Payload

{
  "id": "evt_01HX...",
  "type": "project.resource.linked",
  "created_at": "2026-05-18T10:05:00Z",
  "api_version": "2026-05-01",
  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
  "data": {
    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
    "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",
    "type": "channel",
    "title": "Research Premium Lounge",
    "chat_id": "e41a9b06-2c78-4f3d-95b2-08d7c1a5e934"
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `project.resource.linked` for this event.
`created_at`	ISO 8601 timestamp	Server-side emission time.
`api_version`	string	Webhook API contract version.
`project_id`	string UUID	Project this event belongs to.
`data.project_id`	string UUID	Mirrors top-level `project_id`.
`data.resource_id`	string UUID	Resource identifier.
`data.type`	enum: `channel` \| `group` \| `supergroup`	Telegram chat type at link time.
`data.title`	string	Telegram-side chat title at link time.
`data.chat_id`	string UUID	UUID of the Subscriby `telegram_chats` record, not Telegram's numeric chat id.

Caveats

Re-linking a chat after an unlink creates a new resource row — the project.resource.linked you receive carries a different resource_id than the earlier project.resource.unlinked, and the unlinked row remains behind with chat_id: null.
manual resources cannot be linked; they have no underlying chat.

project.resource.unlinked — paired transition.
project.resource.created — the separate REST / MCP path for manual resources; not a predecessor of this event.
Project events overview — back to family overview.