OpenClaw Telegram, Discord и WhatsApp не работают? Исправление всех проблем интеграции каналов

Your Bot Is Running But Nobody Can Talk to It

You've set up OpenClaw, connected a messaging platform, and... silence. The bot is online, the gateway is healthy, but messages from Telegram groups get ignored, Discord commands return nothing, or WhatsApp bans your number within hours.

Channel integrations are where most OpenClaw deployments break. Each platform has its own authentication model, permission system, and rate limits -- and OpenClaw's documentation doesn't always make the platform-specific requirements obvious.

Here's how to fix every common channel issue across Telegram, Discord, and WhatsApp.

Telegram: Bot Not Responding in Groups

This is the #1 Telegram issue. Your bot works perfectly in direct messages but ignores everything in group chats. The bot is in the group, it shows as a member, but it never responds.

Root Cause: Privacy Mode

Telegram bots have Privacy Mode enabled by default. In this mode, the bot only receives messages that directly mention it (via /command or @botname). All other group messages are invisible to the bot.

Fix: Disable Privacy Mode

1. Open a chat with @BotFather on Telegram
2. Send /mybots and select your bot
3. Go to Bot Settings → Group Privacy
4. Click Turn off

Fix: Grant Admin Rights (Alternative)

If you don't want to disable privacy mode globally, making the bot an admin in a specific group also gives it access to all messages in that group. This is more targeted but requires manual setup per group.

Verify It's Working

After re-adding the bot, send a regular message (not a command) in the group. Check OpenClaw's logs:

docker logs openclaw --tail 50 | grep -i telegram

You should see incoming message events. If you see connection events but no messages, privacy mode is still active or the bot wasn't re-added after the change.

Telegram: Webhook vs Polling Conflicts

OpenClaw can connect to Telegram via webhooks or long polling. Using both simultaneously -- or switching without cleanup -- causes message delivery failures.

Symptoms

• Bot receives some messages but misses others randomly
• Duplicate responses to single messages
• "Conflict: terminated by other getUpdates request" in logs

Fix: Choose One Mode and Clean Up

If you're using polling (default for most self-hosted setups):

# Clear any existing webhook so polling works cleanly
curl -X POST "https://api.telegram.org/bot<YOUR_TOKEN>/deleteWebhook"

If you're using webhooks (better for production):

# Set the webhook to your OpenClaw endpoint
curl -X POST "https://api.telegram.org/bot<YOUR_TOKEN>/setWebhook" \
  -d "url=https://openclaw.yourdomain.com/telegram/webhook"

Discord: Bot Online But Not Reading Messages

Your Discord bot shows as online with a green dot, responds to slash commands, but can't see regular messages in channels. This is a permissions issue introduced by Discord in 2022.

Root Cause: MESSAGE_CONTENT Intent Not Enabled

Discord requires bots to explicitly request the Message Content privileged intent to read the text content of messages. Without it, your bot receives message events but the content field is empty.

Fix: Enable the Intent

1. Go to the Discord Developer Portal
2. Select your bot application
3. Navigate to Bot → Privileged Gateway Intents
4. Enable Message Content Intent
5. Click Save Changes
6. Restart OpenClaw -- the intent is negotiated at connection time

Fix: Update Your OpenClaw Config

Ensure your OpenClaw Discord configuration requests the intent:

{
  "channels": {
    "discord": {
      "token": "your-bot-token",
      "intents": ["GUILDS", "GUILD_MESSAGES", "MESSAGE_CONTENT", "DIRECT_MESSAGES"]
    }
  }
}

If intents isn't specified, OpenClaw may use a default set that doesn't include MESSAGE_CONTENT.

Verify Permissions

The bot also needs these permissions in each channel:

• View Channel -- to see the channel exists
• Read Message History -- to see previous messages
• Send Messages -- to respond

Check with: Server Settings → Integrations → your bot → Manage → Channel permissions

Discord: Rate Limiting and Disconnects

Discord enforces strict rate limits. If your OpenClaw bot sends too many messages too quickly, Discord will throttle or temporarily ban the connection.

Symptoms

• Bot goes offline intermittently
• "You are being rate limited" errors in logs
• Responses delayed by 5-30 seconds randomly

Fix: Implement Response Delays

If you're running workflows that generate rapid responses (like monitoring alerts), add a delay between messages in your OpenClaw agent configuration. Discord's rate limits are typically:

• 5 messages per 5 seconds per channel
• Global rate limit: 50 requests per second across all endpoints

For high-volume use cases, batch updates into a single message instead of sending multiple short messages.

WhatsApp: Account Banned After Setup

WhatsApp is the most fragile channel integration. Using the unofficial Baileys library (which most self-hosted OpenClaw setups rely on) comes with a real risk of account bans.

Why Bans Happen

WhatsApp doesn't offer a free API for bots. The Baileys library reverse-engineers WhatsApp Web's protocol. Meta actively detects and bans accounts using unofficial clients. Common triggers:

• Sending messages to users who haven't messaged you first
• High message volume from a new number
• Rapid-fire automated responses
• Using a freshly created WhatsApp number

Reduce Ban Risk

1. Use a dedicated phone number -- never use your personal number. If it gets banned, you lose the number entirely.
2. "Warm up" the number -- use it manually for 1-2 weeks before connecting to OpenClaw. Send and receive messages normally.
3. Limit outbound messages -- only respond to messages, don't initiate conversations with new contacts.
4. Add delays -- wait 2-5 seconds before responding to simulate human timing.
5. Keep sessions stable -- frequent reconnections and re-authentications increase ban risk.

Fix: Use the Official WhatsApp Business API

For production use, the WhatsApp Business API (via Meta's Cloud API) is the only ban-safe option. It requires:

• A Meta Business account
• A verified phone number
• Compliance with WhatsApp's commerce and messaging policies

It's more work to set up, but your account won't get banned for being a bot.

Multi-Channel: Event Loop Contention

Running Telegram, Discord, and WhatsApp simultaneously on a single OpenClaw instance can cause performance issues even when each channel works fine individually.

Why It Happens

Each channel protocol uses different connection models:

• Telegram polling holds a long-lived HTTP connection, blocking the Node.js event loop during polls
• Discord uses a persistent WebSocket connection with heartbeats
• WhatsApp (Baileys) uses a separate WebSocket connection with its own keep-alive cycle

On a single-core or resource-constrained VPS, these competing connections can starve each other. A slow Telegram poll blocks Discord heartbeats, causing disconnects. A WhatsApp reconnection cycle delays Telegram message processing.

Fix: Resource Allocation

First, ensure your VPS has enough CPU for multi-channel operation:

Channels	Minimum vCPU	Recommended RAM
Single channel	1 vCPU	2 GB
Two channels	2 vCPU	4 GB
Three+ channels	4 vCPU	8 GB

Fix: Use Webhooks Where Possible

Switch from polling to webhooks for any channel that supports it. Webhooks are event-driven (no blocked connections) and use significantly fewer resources:

• Telegram: Supports webhooks natively (requires SSL)
• Discord: Uses WebSocket by default (no webhook alternative for gateway events)
• WhatsApp: WebSocket only (no webhook option for Baileys)

By switching Telegram to webhooks, you free up the event loop for Discord and WhatsApp's WebSocket connections.

Fix: Separate Instances

For maximum reliability, run each channel as a separate OpenClaw instance:

services:
  openclaw-telegram:
    image: openclaw/openclaw:latest
    environment:
      - OPENCLAW_CHANNEL=telegram
    deploy:
      resources:
        limits:
          memory: 2g
          cpus: '1.0'

  openclaw-discord:
    image: openclaw/openclaw:latest
    environment:
      - OPENCLAW_CHANNEL=discord
    deploy:
      resources:
        limits:
          memory: 2g
          cpus: '1.0'

This provides full isolation -- a WhatsApp reconnection storm won't affect your Telegram bot's responsiveness.

Debugging Any Channel Issue

When a channel integration breaks, follow this diagnostic flow:

1. Check OpenClaw gateway status:

curl http://127.0.0.1:18789/api/status

2. Check channel-specific logs:

docker logs openclaw 2>&1 | grep -i "telegram\|discord\|whatsapp"

3. Test the channel token independently:

For Telegram:

curl "https://api.telegram.org/bot<TOKEN>/getMe"

For Discord:

curl -H "Authorization: Bot <TOKEN>" https://discord.com/api/v10/users/@me

A successful response means the token is valid. If the token works but OpenClaw doesn't respond, the issue is in OpenClaw's channel configuration, not the platform.

4. Check network connectivity from your VPS:

# Telegram API
curl -I https://api.telegram.org

# Discord Gateway
curl -I https://gateway.discord.gg

# WhatsApp Web
curl -I https://web.whatsapp.com

If any of these fail, your VPS provider may be blocking the endpoints or the platform may be blocking your VPS IP range.

Channel Integration Quick Reference

Issue	Platform	Fix
Bot ignores group messages	Telegram	Disable Privacy Mode in BotFather, re-add bot
Webhook/polling conflict	Telegram	Delete webhook or stop polling, use one method
Bot online but can't read messages	Discord	Enable MESSAGE_CONTENT intent in Developer Portal
Rate limited / disconnects	Discord	Add response delays, batch messages
Account banned	WhatsApp	Use dedicated number, warm up, limit outbound
Multi-channel slowdown	All	Upgrade VPS, use webhooks, or separate instances
Token works but bot silent	All	Check OpenClaw channel config and intents

VPS Recommendations for Multi-Channel Bots

Running a responsive multi-channel bot requires consistent CPU and low-latency networking:

• Contabo VPS 1 ($4.50/mo): 4 vCPU, 8 GB RAM -- best value for multi-channel deployments
• Hostinger KVM 2 ($8.49/mo): 8 GB RAM, excellent uptime for always-on bots
• Vultr ($5-12/mo): Clean IPs across 32 locations, good for avoiding platform blocks
• DigitalOcean ($6-24/mo): Built-in monitoring to track bot health

Conclusion

Channel integrations are the most fragile part of any OpenClaw deployment. Telegram's privacy mode, Discord's intent system, and WhatsApp's ban-happy enforcement each require specific configuration that isn't obvious from OpenClaw's setup alone.

Fix Telegram by disabling privacy mode and re-adding the bot. Fix Discord by enabling the Message Content intent. Fix WhatsApp by using a warmed-up dedicated number or switching to the official Business API. And if you're running multiple channels, give your VPS enough resources or separate the instances entirely.