Telegram — limited availability

Telegram has limited availability. Operade can validate a bot token, store it as a workspace Secret, receive private text updates, run the agent, send replies, and preserve tested conversation continuity. The customer production setup is not complete, so this page describes verified behavior and the remaining boundary; it is not an activation promise.

Verified configuration and runtime behavior#

The existing configuration accepts either a new bot token or the name of a saved workspace Secret, never both. A new token is validated against Telegram before the channel and Secret are committed. A rejected token leaves neither object behind. The same Telegram bot can belong to only one bot–one agent mapping within a workspace, even if different Secret names contain the same token.

An owner or admin can create the mapping, pause or resume delivery, and delete it. There is no in-place edit for changing the agent or token: delete the channel and recreate it with the intended values. Deletion also means the one-time inbound credential is not recoverable.

The receiver accepts private text messages. Unsupported updates such as group messages, media, buttons, or edits are acknowledged and ignored. Duplicate Telegram updates are idempotent. Quota checks can reject a new segment before a conversation is created.

Production gap and developer-only polling#

Automatic Telegram setWebhook is not automated. Although an HTTP receiver exists and has runtime tests, the HTTP receiver has not been proven through a production end-to-end setup. No customer workflow currently provisions a reachable callback URL with Telegram and verifies delivery from Telegram's network through the deployed service.

The repository's long polling script is a developer tool for local verification. It uses getUpdates and feeds the same inbound handler, but long polling is not the customer production route and should not be operated as a substitute for the missing webhook provisioning. It also requires the one-time inbound credential emitted when the channel is created.

Conversation continuity and limits#

Each Telegram conversation segment obeys the agent's maximum duration, capped at one hour. After a segment ends, a later message from the same sender can create a continuation linked to recent history; the prior closed segment must be within the implemented continuation window. Analysis can read the full continuation chain, while each live runtime segment receives only the supported previous context.

Pause the channel to stop replies without deleting configuration. If Telegram rejects a bot token during setup, verify the token directly with BotFather and try a fresh create. If Operade reports a duplicate bot, find the existing channel and either keep it, pause it, or delete and recreate the intended one-agent mapping.

Do not expose a channel to customers until automated webhook registration and a production end-to-end check are delivered and this availability label changes in the same release. Monitor verified segments through Conversations and filters and inspect inbound/runtime evidence under Transcript and Activity.