Telegram Bot

**Judgement:** Solid, well-documented Telegram Bot integration via the Maton gateway, suitable for most Telegram bot and notification workflows where you’re comfortable depending on an external proxy service and managing an API key. **What it does well** - Wraps the Telegram Bot API with managed authentication: you use a Maton API key and managed connections instead of embedding Telegram bot tokens in your app/skill. - Supports a broad slice of Telegram Bot functionality: text/media messages, polls, locations, contacts, dice, message edit/delete, forwarding/copying, chat info, commands, webhooks, updates, callback queries, and file retrieval. - Good practical docs: clear base URL pattern, environment variable setup, connection management endpoints, and working JS/Python examples. - Multi-bot support via `Maton-Connection` header, which is useful in more complex deployments. **Key risks / limitations** - **External dependency:** All traffic is proxied through Maton (gateway.maton.ai / ctrl.maton.ai). Reliability, latency, and uptime depend on that service as well as Telegram. - **Account and key management:** Requires a Maton account and secure handling of `MATON_API_KEY`. Mismanagement can expose all linked Telegram bots. - **Data routing and privacy:** Messages and metadata transit through a third-party gateway. For sensitive or regulated use cases, this may require additional review or may be unacceptable. - **Telegram constraints:** Still subject to Telegram’s rate limits, anti-spam policies, and message size limits; misuse (e.g., broadcast spam) can result in bans. **Recommended scenarios** - You want to integrate Telegram into an OpenClaw-based agent without directly handling or exposing Telegram bot tokens. - You need a general-purpose Telegram bot backend for notifications, basic chatbots, interactive menus, or polls, and you’re comfortable with Maton as an intermediary. - You operate multiple Telegram bots and value centralized connection management and a unified API key. **Less suitable when** - You must avoid third-party gateways for security, compliance, or data residency reasons (direct Telegram Bot API access would be preferable). - You require ultra-low-latency, high-throughput messaging where the extra hop through Maton could be a bottleneck or single point of failure.