Communication · wired today
Telegram Bot, wired into your agent workforce
Messages and calls are where work actually gets decided. The Telegram Bot connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
Connecting Telegram Bot takes one credential
You provide bot token from your Telegram Bot account; Quox sends it as a credential embedded in the endpoint path. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Telegram Bot's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Telegram Bot
get_meGet the authenticated Telegram bot's own identity and capability flags
get_chatGet metadata for one Telegram chat (group, supergroup, channel or private chat)
get_chat_member_countGet the number of members in one Telegram chat
get_updatesRead pending Telegram updates (incoming messages and events) without long polling
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
Telegram Bot answers every unauthenticated request identically, so its endpoint paths rest on Telegram Bot's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.
Telegram Bot integration FAQ
What can Quox agents do with Telegram Bot?
Agents can run 4 read-only tools against Telegram Bot: get me, get chat, get chat member count, get updates. Every call is receipted in the evidence trail.
What does the Telegram Bot integration need?
You provide bot token from your Telegram Bot account; Quox sends it as a credential embedded in the endpoint path. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Telegram Bot credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Telegram Bot connector?
Telegram Bot answers every unauthenticated request identically, so its endpoint paths rest on Telegram Bot's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.