OneClickClaw.io
One token, one pairing code, no terminal

OpenClaw Telegram Setup Without Server Setup

Connecting OpenClaw to Telegram is genuinely easy. Keeping it connected is the hard part, because a Telegram bot only answers while something, somewhere, is running. Most guides for this send you through provisioning a VPS, installing Node, setting up a process manager, and issuing a certificate before you reach the interesting bit. This one skips all of it: the server is already running, so the setup is a token and a pairing code.

The five steps

Steps one, two, four and five happen in Telegram; step three is a single paste in your dashboard. Allow about five minutes.

  1. Create the bot with BotFather

    In Telegram, search for @BotFather and open the chat, checking for the blue verified badge. Send /newbot, choose a display name your contacts will see, then a username that ends in “bot”. Usernames are unique across Telegram, so expect to try a couple.

  2. Copy the HTTP API token

    BotFather replies with a token shaped like 123456789:ABCDefGhIJKlmNOpQrSTUvWxYz. Treat it as a password: anyone holding it controls your bot. Do not paste it into a public chat or a screenshot.

  3. Paste it into your OneClickClaw dashboard

    Open your agent, go to Channels, choose Add Telegram, paste the token, and save. The token is validated and the configuration is pushed to your own server automatically. The status indicator turns green when the channel is live.

  4. Send a first message and approve the pairing code

    Message your new bot. Instead of replying immediately it returns a one-time pairing code, and the agent stays silent until you approve that code in your dashboard. This is the step that stops a stranger who guesses your bot username from talking to your agent.

  5. Test it, then decide about groups

    Once paired, send a normal question and you should get an answer within a few seconds. To use the bot in a group, add it like any member. If it should read all group messages rather than only commands, send /setprivacy to BotFather and set privacy mode to Disable, and only do that in groups whose membership you control.

The same walkthrough with dashboard screenshots lives in the docs: Telegram setup in the OneClickClaw docs.

The step most guides skip: who is allowed to talk to it

Every Telegram bot is publicly addressable. Once your bot exists, anyone who knows or guesses its username can open a chat with it and start typing. If your agent answered all of them, you would be paying for strangers' model usage and handing them an assistant that may have access to your files and tools.

That is what the pairing step is for. A new chat gets a one-time code instead of an answer, and the agent stays silent until you approve that code from your dashboard. It costs you ten seconds once and it is the difference between a private assistant and an open one.

Two habits are worth forming alongside it. Approve only codes you were expecting, because an unexpected code means someone found your bot. And keep the bot token private, since anyone holding it can drive the bot regardless of pairing; if it ever leaks, regenerate it through BotFather and paste the new one in. The wider picture, including which controls are ours and which stay yours, is set out in the OpenClaw VPS security checklist.

What "without server setup" actually replaces

If you were doing this yourself on a bare VPS, the Telegram part would still be five minutes. Everything below is the work that surrounds it, before the bot is reliable enough to depend on.

A server that never sleeps

A Telegram bot only answers while its process is running. A laptop that closes or a free tier that idles out means a bot that silently stops replying.

The install and the plumbing

Node 22 or newer, OpenClaw installed and configured, a process manager such as PM2 so it restarts after a crash or reboot, an nginx reverse proxy, and a certificate from certbot.

Keeping it safe afterwards

Firewall rules, an encrypted place for your API keys, security updates for both the OS and OpenClaw, and backups you have actually tested.

Being the on-call engineer

Noticing when it goes down, and fixing it. This is the part that does not appear on any VPS invoice and costs the most.

None of that is difficult for someone who runs servers already, and if that is you, the managed versus do-it-yourself comparison lays out both paths without pretending one is right for everyone. What managed hosting buys is that the list above is somebody else's job, permanently, on a dedicated EU VPS that is yours alone.

Telegram troubleshooting and FAQ

My bot does not reply. What is the first thing to check?
Almost always the pairing step. OpenClaw answers a new Telegram chat only after the pairing code from that chat has been approved in your dashboard, so a bot that responds once with a code and then goes quiet is behaving correctly and waiting for you. If you have approved the code and it is still silent, check that the AI provider key on the agent is valid, because a rejected key produces a live channel with no replies.
Do I need a server, a domain, or a webhook URL?
Not with managed hosting. You never provision a server, install Node, configure nginx, or register a webhook: your dedicated VPS is created and configured for you, and the Telegram connection is made from the dashboard with the bot token. If you self-host, all of that is yours to set up and maintain.
Can anyone who finds my bot username talk to my agent?
They can send it messages, because that is how Telegram works for every bot. They cannot get answers from your agent unless you approve their pairing code. This is why the pairing step exists and why you should only approve codes you recognise.
How do I use the bot in a group chat?
Add the bot to the group the same way you add any member. By default Telegram's privacy mode limits a bot to seeing commands rather than all messages; sending /setprivacy to BotFather and setting it to Disable lets it read the conversation. Only do this in groups whose membership you control, since it means the agent sees everything posted there.
Can I run Telegram and other channels on the same agent?
Yes. The same agent can serve multiple channels at once, so a Telegram bot and, for example, WhatsApp or Discord can share one instance, one provider key, and one set of instructions. OpenClaw supports a wide range of channels beyond the three the dashboard sets up for you.
What does this cost to keep running?
Hosting starts at EUR 14.99 per month for the Starter plan, which is a dedicated EU server that stays online so the bot can answer at any hour. Telegram itself is free, and the AI model usage is billed to you directly by your own provider under BYOK. The cost guide breaks down both parts and shows how to estimate and cap the variable one.

Still stuck? The docs cover channel connection problems in more depth.

Keep exploring

OpenClaw Telegram Setup Without Server Setup