How to connect Telegram Bot to Grok Bot
Connect Telegram Bot to Grok Bot with ClawLink: paste your Telegram Bot key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
Telegram BotAPI KEYMCPAutomate Telegram chats and channels through a Telegram Bot. Requires a bot token from @BotFather.. Once connected, Grok Bot can read and act on Telegram Bot from chat — pairing, token refresh, and tool wiring handled for you.
Grok Bot runs on its own cloud computer, so most Telegram Bot guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Telegram Bot setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Telegram Bot actions from chat with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Grok Bot. It runs the ClawLink CLI in its own terminal and pairs your account.
Set up ClawLink for me and tell me when it's ready.
1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait:
npx -y @useclawlink/cli login
2. I'll approve it in my browser, then reply "approved".
3. When I say approved, connect the app:
npx -y @useclawlink/cli connect telegram
4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Grok Bot to Telegram Bot.
1Pair from the terminal
Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:
npx -y @useclawlink/cli login- 2
Connect Telegram Bot
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Grok Bot: "What can you do with Telegram Bot?"
Install by command
The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:
npx -y @useclawlink/cli login # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect telegramPair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.
Verify the connection by asking Grok Bot:
Use Telegram Bot to answer callback query and walk me through the result in plain English.
Using a different agent?
The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Telegram Bot is connected in the dashboard, that agent calls the same 18 Telegram Bot tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Telegram Bot MCP for Grok Bot
Looking for a Telegram Bot MCP server for Grok Bot? ClawLink connects Telegram Bot to Grok Bot and exposes 18 Telegram Bot tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw Telegram Bot integration and the Hermes Telegram Bot integration connect the same ClawLink account the same way.
What the Grok Bot Telegram Bot integration can do
18 Telegram Bot tools are ready for Grok Bot once the account is connected. The 17 below are the ones people reach for most; your agent can call all 18.
17 of 18 Telegram Bot tools for Grok Bot
| Tool | What it does |
|---|---|
Answer callback query telegram_answer_callback_query | Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. |
Create chat invite link telegram_create_chat_invite_link | Generate a new primary invite link for a chat; any previously generated primary link is revoked. |
Edit message telegram_edit_message | Edit text messages sent by the bot. Only bot-authored messages can be edited; editing messages from other users will fail. In groups, the bot must have edit permissions. |
Forward message telegram_forward_message | Forward messages of any kind. Service messages can't be forwarded. |
Get chat telegram_get_chat | Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). |
Get chat administrators telegram_get_chat_administrators | Get a list of administrators in a chat. On success, returns an Array of ChatMember objects containing information about all chat administrators except other bots. |
Get chat history telegram_get_chat_history | Get chat history messages via the getUpdates polling method, filtered by chat_id. Returns only updates from the specified chat. |
Get chat member telegram_get_chat_member | Get a chat member's status/role (including the bot itself) to preflight permissions and troubleshoot 403/empty-history issues. Use before sending messages to verify bot membership and permissions. |
Get chat members count telegram_get_chat_members_count | Get the number of members in a chat. The bot must be an administrator in the chat for this to work. Insufficient admin permissions surface as authorization errors, not as a zero or empty count. |
Get me telegram_get_me | Get basic information about the bot using the Bot API getMe method. Returns fields like id, username, first_name, and capabilities. |
Get updates telegram_get_updates | Use this method to receive incoming updates using long polling. An Array of Update objects is returned. IMPORTANT: This method will not work if an outgoing webhook is set up. |
Send document telegram_send_document | Send general files (documents) to a Telegram chat using the Bot API |
Send location telegram_send_location | Send point on the map location to a Telegram chat using the Bot API |
Send message telegram_send_message | Send a text message to a Telegram chat using the Bot API |
Send photo telegram_send_photo | Send photos to a Telegram chat using the Bot API |
Send poll telegram_send_poll | Send a native poll to a Telegram chat using the Bot API |
Set my commands telegram_set_my_commands | Use this method to change the list of the bot's commands |
Try it: find the Telegram Bot tool you need
Browse the 17 Telegram Bot tools
Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.
Example prompts
Use Telegram Bot to answer callback query and walk me through the result in plain English.
Create it in Telegram Bot for me, then confirm the important fields before you finish.
Use Telegram Bot to edit message and walk me through the result in plain English.
Use Telegram Bot to forward message and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Telegram Bot working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Telegram Bot API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Telegram Bot account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Telegram Bot. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Telegram Bot actions to the runtime in a format your agent can reliably use. | 18 tools for Telegram Bot are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Telegram Bot to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Telegram Bot in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Telegram Bot key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
Connection succeeds but no tools appear
Reconnect Telegram Bot from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Telegram Bot tools
Telegram Bot tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Telegram Bot call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Telegram Bot returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Telegram Bot has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Grok Bot Telegram Bot integration?
Yes. ClawLink is the fastest way to connect Grok Bot to Telegram Bot: link your Telegram Bot account once in the browser and Grok Bot can call the Telegram Bot API through 18 ready-made tools — no custom code or token handling.
How do I connect Telegram Bot to Grok Bot with ClawLink?
Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal and approve the link it prints, then npx -y @useclawlink/cli connect telegram to authorize Telegram Bot. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files, and the Telegram Bot key you paste is stored server-side instead of in your environment.
How long does it take to connect Telegram Bot to Grok Bot?
About two minutes. Sign in, click Connect next to Telegram Bot in the dashboard, authenticate, and Grok Bot can use it from the next chat message.
Why use ClawLink instead of wiring Telegram Bot up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Telegram Bot working from chat.
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
