Connect OpenClaw to WhatsApp

WhatsApp pairing creates session state that must survive Gateway restarts. Use a dedicated test conversation first and protect the state directory like a credential.

Pair through the supported flow

Follow the channel setup presented by your installed OpenClaw version and scan the QR code with the intended WhatsApp account. Do not share a pairing QR or session files.

Keep state persistent

On a server or container, make sure the OpenClaw state directory is persisted and owned by the user running the Gateway. Recreating an ephemeral container can otherwise look like a mysterious channel logout.

Verify transport

openclaw gateway status
openclaw channels status --probe
openclaw logs --follow

Expected result

The channel reports connected transport, the session survives a controlled Gateway restart, and a message from the allowed test account receives a reply.

If messages stop after previously working, verify Gateway health before pairing again. Repeated re-pairing can hide a state-volume or service ownership problem.