WhatsApp | OpenClaw

Channels 3 sections 3 key facts

WhatsApp Web

OpenClaw currently connects to WhatsApp through Baileys and a WhatsApp Web session owned by the Gateway. It is the most common real-world entry point, but it is more dependent on QR login, device state and credential persistence than Telegram.

Channels Pairing Channel Troubleshooting

Two Ways to Use It

Dedicated Recommended

Dedicated number

The cleanest and safest path. Use a separate number or WhatsApp Business account so personal chats stay isolated from the assistant.

Fallback

Self-chat on a personal number

Possible as a temporary route, but you must explicitly enable selfChatMode so pairing and normal contacts are not accidentally affected.

Common Config and Operations

Minimal allowlist config

{
  channels: {
    whatsapp: {
      dmPolicy: "allowlist",
      allowFrom: ["+15551234567"]
    }
  }
}

Login and relogin

openclaw channels login
openclaw channels logout
openclaw channels login --verbose

Important Notes

Login is completed by QR scan, and credentials are usually written to ~/.openclaw/credentials/whatsapp/<accountId>/creds.json.

Unknown direct messages do not get processed immediately. They receive a pairing code first and only enter the agent after approval.

Sending depends on an active listener and live session. When logs show loggedOut or status codes in the 409-515 range, you often need to relink.

The older Twilio route is no longer the recommended path. WhatsApp Web is the main OpenClaw route today.