Messaging
Telegram
A Telegram integration connects a Telegram bot to Mobius so loops can receive bot updates as source events and send Telegram replies from action steps.
Use Telegram when a run should start from a bot message or when a loop should respond in the same chat after completing bounded work.
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.
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
- Match bot messages with triggers.
- Resume existing runs with wait steps.
- Inspect provider delivery with source events.