OpenClaw Telegram Setup Guide

Telegram is still the fastest way to verify that OpenClaw is installed correctly, the gateway can answer messages, and your first real channel workflow is ready. This guide covers the full OpenClaw Telegram setup flow, from bot creation and bot token configuration to restart, pairing, and no-reply troubleshooting.

Why start with Telegram

Telegram is usually the easiest OpenClaw channel to validate after installation
You only need a bot token and one successful reply to confirm the gateway loop is working
It is a practical first step before you add more channels, skills, or browser relay workflows

What you’ll achieve

Create a Telegram bot and get the Bot Token
Enable Telegram channel in OpenClaw
Restart gateway and verify responses
Fix common issues such as no replies, blocked network access, and pairing failures

Step 0: Ensure the OpenClaw gateway is running

Command

openclaw gateway status || trueopenclaw gateway --detach

If the gateway is already running, this check confirms that your OpenClaw runtime is available before you connect Telegram. If the process does not stay up, go to /docs/troubleshooting first.

Step 1: Create a bot with BotFather

Search for @BotFather
Run /newbot
Copy the Telegram Bot Token you receive

Step 2: Configure the Telegram bot token

Command

openclaw config set channels.telegram.botToken "YOUR_TELEGRAM_BOT_TOKEN"openclaw config set channels.telegram.enabled true

This is the key OpenClaw Telegram setting. If the token is wrong or missing, the bot may appear online but normal messages will never receive a reply.

Step 3: Restart the gateway

Command

openclaw gateway restart

Restarting forces the gateway to reload the updated Telegram channel config. If you skip this step, your new bot token may not be picked up.

Step 4: Test in Telegram

Find your bot
Send /start
Send a normal text message and confirm the bot replies

Step 5: Approve pairing if required

Command

openclaw pairing approve telegram <PAIRING_CODE>

Fix no replies, blocked networks, or token issues

Re-check the saved bot token with openclaw config get channels.telegram.botToken
Restart the gateway again after each Telegram config change
Confirm your server can reach https://api.telegram.org
If the bot still does not answer, compare the gateway token and runtime checks in /docs/advanced-config and /docs/troubleshooting

Proxy tip for restricted networks

Command

export https_proxy=http://127.0.0.1:7890export http_proxy=http://127.0.0.1:7890openclaw gateway restart

Troubleshooting: /docs/troubleshooting
Advanced allowlists, gateway token, and browser relay: /docs/advanced-config
OpenClaw FAQ: /faq
OpenClaw skills and workflow ideas: /skills and /use-cases