| name | telegram-automation |
| description | Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | communication-content |
| category | social-media |
| risk | critical |
| source | community |
| tags | ["skill","communication-content","social-media","telegram","automation"] |
Telegram Automation via Rube MCP
Automate Telegram operations through Composio's Telegram toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Telegram connection via
RUBE_MANAGE_CONNECTIONS with toolkit telegram
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
- Telegram Bot Token required (created via @BotFather)
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit telegram
- If connection is not ACTIVE, follow the returned auth link to configure the Telegram bot
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Send Messages
When to use: User wants to send text messages to a Telegram chat
Tool sequence:
TELEGRAM_GET_ME - Verify bot identity and connection [Prerequisite]TELEGRAM_GET_CHAT - Get chat details and verify access [Optional]TELEGRAM_SEND_MESSAGE - Send a text message [Required]
Key parameters:
chat_id: Numeric chat ID or channel username (e.g., '@channelname')text: Message text contentparse_mode: 'HTML' or 'MarkdownV2' for formattingdisable_notification: Send silently without notification soundreply_to_message_id: Message ID to reply to
Pitfalls:
- Bot must be a member of the chat/group to send messages
- MarkdownV2 requires escaping special characters:
_*[]()~>#+-=|{}.!
- HTML mode supports limited tags:
<b>, <i>, <code>, <pre>, <a>
- Messages have a 4096 character limit; split longer content
