Channel recipe · Independent guidance

Set up an OpenClaw WhatsApp assistant

WhatsApp support is an external official plugin. Install through onboarding or the channel command, link by QR, keep the default DM pairing or an explicit E.164 allowlist, and probe the channel before using groups or automations. Use an isolated test account where platform/account risk matters.

Live retest required · noindexUpdated 2026-08-24Documentation-reproduced checklist · isolated live account retest required
01

Link with bounded access

  1. 1

    Install through the channel flow

    The current CLI can prompt to install the official external plugin.

    openclaw channels add --channel whatsapp
  2. 2

    Link by QR

    Use a live terminal path; QR images can expire in transit.

    openclaw channels login --channel whatsapp
  3. 3

    Approve the first DM

    Pairing requests expire and should be checked against the expected sender.

    openclaw pairing list whatsapp
    openclaw pairing approve whatsapp <CODE>
  4. 4

    Probe health

    Verify linked state, Gateway, and channel runtime before an automation.

    openclaw channels status --probe
    openclaw doctor --json
02

Failure and rollback

  • Back up the account auth directory before relinking when troubleshooting a production account.
  • Disable delivery automation before changing the linked account or allowlist.
  • Log out the exact account to stop the live listener and clear its WhatsApp auth state.
  • Treat WhatsApp platform limits and account enforcement as external risk; this recipe cannot promise ban-free operation.
openclaw channels logout --channel whatsapp --account <accountId>

Common questions

Before you act

Can this site display or store the QR?

No. Linking happens in your OpenClaw terminal. This site has no channel connection or account storage.

Primary sources

Verify against the owner.

Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.