Introducing the Official WhatsApp Plugin for OpenClaw: Connect AI Agents in Under 2 Minutes

The first option is to use an unofficial library like Baileys, which connects through WhatsApp's reverse-engineered web protocol. It works — until it doesn't. It violates WhatsApp's Terms of Service, breaks every time WhatsApp updates its clients, and can result in a permanent ban on the developer's personal phone number. For anyone serious about shipping a product, that's not acceptable.

The second option is the official path: apply for your own WhatsApp Business API access through Meta, complete the multi-day Business verification process, manage your own webhook infrastructure, and handle Meta Cloud API tokens securely. For an enterprise team with dedicated developers, that's manageable. For a solo builder shipping an AI agent prototype, it's a wall.

There has been no fast, official, low-friction path between the two. We built one.

There is no Meta Business verification to complete. No API tokens to provision. No webhook server to host. imBee runs the verified WhatsApp Business Account (WABA), the routing infrastructure, and the security layer. Your local OpenClaw instance pairs to imBee's number through a one-time QR-code flow, and from then on every message sent to that number is forwarded to your agent in under 500 milliseconds.

The plugin is distributed through the ClawHub registry and npm. Install with one command:

openclaw plugins install openclaw-channel-whatsapp-official

It then appears as a first-class channel option inside the standard openclaw channels add setup wizard, alongside any other channels you have installed.

1. Choose the channel. When you run openclaw channels add, the plugin appears as “Official WhatsApp API (via imBee)” in the channel selection menu.
2. Get your pairing code. The plugin makes an authenticated HTTPS request to imBee's routing server, which generates a short-lived, cryptographically random code (for example, CLAW-A3F9-Z7KL) and returns it along with a per-instance API key.
3. Scan the QR code. The terminal renders a QR code and a wa.me deep link. Both contain imBee's verified WhatsApp Business number and your unique pairing code.
4. Send the code from your phone. Scan the QR code or tap the link on your mobile device. WhatsApp opens with the pairing code pre-filled. Tap Send.
5. Pairing completes server-side. imBee's routing server receives the message, validates the code, creates a permanent mapping between your phone number and your local OpenClaw instance, and sends a confirmation back to your phone.
6. Your agent is live. The setup wizard exits with a success message. Every subsequent WhatsApp message sent to imBee's shared number is routed to your agent in real time.

The pairing code is single-use, expires in 10 minutes, and is generated from 36⁸ ≈ 2.8 trillion combinations. Once your instance is paired, the code is invalidated and never persisted on your machine.

When a WhatsApp message arrives at imBee's verified number, our routing server identifies the paired local instance and forwards the full event over a persistent WebSocket connection in under 500 milliseconds. For text messages, your agent also gets a typing indicator sent back to the user automatically — so customers see “typing…” while your agent processes the request.

Supported inbound message types:

• Text — passed straight to your agent
• Image — embedded as a base64 data URI, readable by vision models like GPT-4V and Claude 3.5 Sonnet
• Video — described to your agent with metadata (filename, MIME type, file size)
• Audio and voice notes — described to your agent for voice-aware processing
• Sticker — described with metadata
• Document — described with filename, MIME type, and file size

Outbound responses go through a single REST call to imBee's routing server, which then delivers via the WhatsApp Cloud API. Your agent can send text or media — images, video, audio, or documents — without touching Meta or 360dialog directly.

Every connection between your local plugin and imBee's routing server uses TLS 1.2 or higher. The WebSocket connection uses wss://. Your local instance authenticates with a per-instance Bearer token generated during pairing, stored in OpenClaw's credential store via the SecretRef surface — never in plain text on disk.

Webhook integrity is verified on every inbound event: HMAC-SHA256 against Meta's app secret for the Meta Cloud API backend, or Ocp-Apim-Subscription-Key validation for the 360dialog backend. Any request that fails these checks is rejected with 403 Forbidden.

Most importantly: message content is never persistently stored on imBee's routing server. Payloads are processed in memory and forwarded to your local instance immediately. The only data we persist is the routing metadata — phone number, WABA number, instance ID, and connection status — necessary to deliver future messages to the right agent.

This is the same security posture imBee delivers to enterprise customers in Financial Services, Healthcare, and Logistics. The plugin inherits it by design.

For developers building on OpenClaw, install via ClawHub or npm:

openclaw plugins install openclaw-channel-whatsapp-official

Then run:

openclaw channels add

Select Official WhatsApp API (via imBee) from the menu, scan the QR code with your phone, and send the pairing code from WhatsApp. That's the entire setup.

For enterprises evaluating WhatsApp as part of a broader AI agent strategy — and wondering how imBee's BSP-grade infrastructure can scale to dedicated numbers, multi-agent routing, broadcast campaigns, and the rest of imBee's omnichannel platform — Book a demo with our team. We help enterprises across Asia-Pacific connect AI to customer conversations at scale, securely.

The Official WhatsApp Plugin for OpenClaw is available now via ClawHub and the GitHub repository.