Telegram setup

Route

Bot API: sendMessage (text), sendPhoto, sendVideo (MP4 plays inline; other video formats are sent as a file via sendDocument and the receipt says so). Telegram has no way to read a sent message back, so a Telegram post is recorded on the send response — Telegram posts are never described as read-back verified.

Connecting

No app registration and no review: create a bot with @BotFather, copy its token, add the bot to your channel as an administrator with “Post Messages” (or to your group), then paste the token and the channel's @username or numeric id. The token is a secret — anyone holding it controls the bot — so it is stored encrypted and never shown again.

No server variables are needed for this platform; the credential is verified against the platform before it is stored, then encrypted at rest.

Scopes

None: the bot posts where it is an administrator with the posting right.

Limits the engine enforces

4,096 characters for text, 1,024 for a caption on media; 50 MB per video or file, 10 MB per photo; about 20 messages per minute in a group, and Telegram's retry_after is honoured.

Review gate

None. Telegram has no approval clock for bots. If a send's answer is lost, the post stays uncertain until a workspace owner or admin forces a retry or marks it resolved — Telegram offers no way to check. A listing of our assistant connector in any AI directory does not change this: directory approval is not platform approval.