Documentation Index
Fetch the complete documentation index at: https://orbit-docs.devotel.io/llms.txt
Use this file to discover all available pages before exploring further.
Telegram
Orbit’s Telegram channel wraps the Telegram Bot API so you can send and receive messages, photos, documents, inline keyboards, and callbacks from the same unified Messaging surface used for every other channel. Each Orbit organization can attach one or more bots; webhook delivery is automatic.Send a message
Response
Capabilities
- Text + media — text (with HTML / MarkdownV2 formatting), photo, video, audio, document, voice, animation, sticker.
- Inline + reply keyboards —
inline_keyboard,reply_keyboard, plusforce_replyandremove_keyboard. - Callbacks —
callback_queryevents surfaced astelegram.callbackwebhooks; auto-answerCallbackQueryis handled by Orbit so the spinner clears in the user’s client. - Chat actions —
typing,upload_photo, etc., either via the API or auto-emitted by Orbit when a long-running send is in flight. - Edit + delete — the
PATCH /messages/:idandDELETE /messages/:idendpoints translate toeditMessageTextanddeleteMessage. - Inline mode + bot commands — registered via the bot setup wizard;
/startdeep-links land on your conversation routing rules. - Webhook security — Telegram’s
secret_tokenheader is validated against the per-bot secret stored in Orbit’s encrypted credential vault.
Onboarding flow
- Talk to @BotFather and create a bot. Save the token it returns.
- From the dashboard, navigate to Channels → Telegram → Add bot and paste the token.
- Orbit auto-registers the webhook URL
https://orbit-api.devotel.io/api/v1/webhooks/inbound/telegramand rotates thesecret_tokenheader value. - Optional: configure inline mode and the bot command list directly from the channel detail page.
Common errors
| Code | HTTP | Cause | Fix |
|---|---|---|---|
TG_INVALID_TOKEN | 401 | The bot token has been revoked or rotated by BotFather. | Issue a new token via /revoke in BotFather, then update credentials in the dashboard. |
TG_CHAT_NOT_FOUND | 404 | The chat id no longer exists or the user has blocked the bot. | Skip the recipient; this is permanent until the user re-engages. |
TG_FORBIDDEN_BY_USER | 403 | The user has explicitly blocked the bot. | Mark the contact as opted-out; do not retry. |
TG_FILE_TOO_LARGE | 413 | Attachment exceeds 50 MB (text-API) / 2 GB (Bot API). | Use the file upload endpoint to chunk, or host externally and send a URL. |
TG_FLOOD_WAIT | 429 | Too many requests in a short window. | Honour the Retry-After header — Telegram’s flood-control is strict. |