project.resource.linked
An existing Telegram chat is linked to a project as a resource.
When this fires
A creator binds an existing Telegram channel, group, or supergroup to a previously created resource — typically by inviting the project bot as admin and confirming the link.
Required ability
project-resource:view-any — 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": "prj_01HX...",
"data": {
"project_id": "prj_01HX...",
"resource_id": "rsr_01HX...",
"type": "channel",
"title": "Research Premium Lounge",
"chat_id": "-1001234567890"
}
}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 ULID | Project this event belongs to. |
data.project_id | string ULID | Mirrors top-level project_id. |
data.resource_id | string ULID | 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 | Telegram chat id. |
Caveats
- A resource can be unlinked and re-linked. Each transition emits its own event; use
MP-Event-Idfor dedupe. manualresources cannot be linked; they have no underlying chat.
Related events
project.resource.unlinked— paired transition.project.resource.created— predecessor.- Project events overview — back to family overview.
How is this guide?