#telegram thread
1 messages · Page 1 of 1 (latest)
You’ll usually need a bit of OpenClaw-side config — it’s not “just add the bot and start chatting” (because OpenClaw defaults to being conservative in groups).
1) Telegram-side: you already did the key bit
- Privacy mode = disabled (BotFather
/setprivacy→ Disable) or make the bot an admin. - After changing privacy mode, remove + re-add the bot to the supergroup so Telegram applies it.
Source: https://docs.openclaw.ai/channels/telegram (see “Privacy mode and group visibility”)
2) OpenClaw-side: you must allow the group (and usually the sender)
By default, Telegram groupPolicy is allowlist, so OpenClaw will ignore groups until you configure them.
Minimal pattern (safe default: only respond when mentioned):
{
channels: {
telegram: {
enabled: true,
// botToken: "...",
groups: {
"*": { requireMention: true }
}
}
}
}
Then, depending on what you want:
- Only you can trigger it in the group: set
groupAllowFrom(or rely onallowFromfallback if you already set that for DMs). - Anyone in the group can trigger it: set per-group
groupPolicy: "open".
Docs section: https://docs.openclaw.ai/channels/telegram (tabs “Group policy and allowlists” + “Mention behavior”)
3) Topics: you can just chat in the right topic — but “mentioning agents” won’t route by itself
Telegram forum topics are separate sessions in OpenClaw automatically.
If what you want is “Topic A goes to Agent A, Topic B goes to Agent B”, you should map topics → agents in config:
{
channels: {
telegram: {
groups: {
"-1001234567890": {
topics: {
"1": { agentId: "main" }, // General
"3": { agentId: "dev" }, // Dev topic
"5": { agentId: "ops" } // Ops topic
}