Messaging
Telegram
A Telegram integration connects a Telegram bot to Mobius. Agents can answer bot messages through durable sessions, and loops can receive bot updates or send Telegram replies.
Use Telegram for agent messaging when the conversation should stay open. Use a loop when a bot message should start a bounded process.
Capability map
| Capability | Value |
|---|---|
| Provider ID | telegram |
| Auth kind | api_key |
| Connect flow | Inline bot token |
| Actions | Yes |
| Events | Yes |
| Webhook delivery | Yes |
| Event samples | Yes |
| Live status | Yes |
Connect Telegram
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose Telegram, and paste the bot token. |
| CLI | The mobius CLI does not connect Telegram integrations yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/telegram/connect with the Telegram credential body from the API reference. |
Mobius configures the bot webhook for provider delivery. A live-status check shows the upstream webhook state when messages are not arriving.
Agent messaging
Connect Telegram, then add a messaging binding to the agent that should answer. The binding decides whether the agent responds to direct messages, mentions, or selected conversations. Telegram replies are stored in the same durable session transcript as API and Slack messaging.
For group chats with mention activation, Mobius recognizes an exact
@bot_username, Telegram's structured mention and text_mention entities,
and replies to a message the bot sent. Media captions count as message text, so
a caption that mentions the bot can activate the agent too. Start with mention
activation before enabling all group messages; it keeps a busy chat from
starting turns accidentally.
Actions
telegram.message.sendUse telegram.message.send to reply into the chat that started the run or to
notify a fixed chat ID.
Events
telegram.callback_query.received
telegram.channel_post.received
telegram.message.edited
telegram.message.receivedUse telegram.message.received for conversational intake. Use callback-query
events when inline buttons should resume a run or start follow-up work.
Next
- Route bot messages to agents with agent messaging.
- Match bot messages with triggers.
- Resume existing runs with wait steps.
- Inspect provider delivery with source events.