How to Connect WhatsApp to OpenClaw — Step-by-Step 2026 Guide

Getting WhatsApp connected to OpenClaw is the most powerful — and the most involved — channel integration you can make. Unlike Telegram, which requires just a bot token, WhatsApp uses Meta’s Business API and requires several layers of verification. This guide explains every step, including the parts that frequently trip people up.

Why WhatsApp Is Worth the Effort

WhatsApp has over 2 billion active users. For many people and businesses, it’s the primary communication channel. Connecting it to your self-hosted OpenClaw AI assistant means you can have intelligent, context-aware AI responses arrive directly in WhatsApp conversations — without routing your messages through any third-party AI platform.

Prerequisites

Before you start:

• A working OpenClaw instance running on port 18789 with a publicly accessible HTTPS URL
• A Meta Business Account (business.facebook.com)
• A phone number that is not currently registered to a personal WhatsApp account
• A Meta Developer account (developers.facebook.com)

Step 1: Create a Meta App in the Developer Console

Go to developers.facebook.com and click Create App. Select Business as the app type. Give it a name like “OpenClaw AI” and associate it with your Meta Business Account.

Once the app is created, scroll to find the WhatsApp product and click Set Up.

Step 2: Add a Phone Number

In the WhatsApp setup panel, navigate to Phone Numbers and click Add Phone Number. You will need to verify the number via SMS or voice call. This step requires a real phone number — virtual numbers from some providers are rejected by Meta.

Important: once a phone number is registered to the WhatsApp Business API, it cannot simultaneously run regular WhatsApp on a phone. Plan accordingly.

After verification, Meta assigns you a Phone Number ID and a WhatsApp Business Account ID — save both.

Step 3: Generate a Permanent Access Token

In the Meta Developer Console, navigate to System Users under your Business Settings. Create a system user with Admin role, then generate a permanent token with the whatsapp_business_messaging and whatsapp_business_management permissions. Save this token securely — it is your WhatsApp API access token.

Avoid using a temporary token (the kind shown on the Getting Started page) — it expires in 24 hours and will break your integration.

Step 4: Configure the Webhook

OpenClaw needs to receive incoming messages from Meta via a webhook. In the Developer Console, go to Configuration → Webhooks and set:

• Callback URL: https://your-openclaw-domain.com/webhook/whatsapp
• Verify Token: a secret string you choose (e.g., a random 32-character string)

Subscribe to the messages field under the whatsapp_business_account object.

Meta will send a GET request to your webhook URL to verify it. OpenClaw handles this verification automatically — ensure your instance is running and the URL is reachable before saving.

Step 5: Add WhatsApp to OpenClaw Config

Open your OpenClaw configuration file at config/openclaw.yaml and add the WhatsApp channel block:

channels:
  whatsapp:
    enabled: true
    phone_number_id: "YOUR_PHONE_NUMBER_ID"
    business_account_id: "YOUR_WABA_ID"
    access_token: "YOUR_PERMANENT_ACCESS_TOKEN"
    verify_token: "YOUR_WEBHOOK_VERIFY_TOKEN"

Restart OpenClaw via PM2:

pm2 restart openclaw

Step 6: Business Verification (If Required)

Meta may require you to complete Business Verification before moving beyond the sandbox. This involves submitting business documents (registration certificate, utility bill) through the Meta Business Manager. Verification typically takes 3–7 business days.

Until verification is complete, you can send messages to up to 5 test numbers added in the Developer Console.

Common Pitfalls

• Webhook not verifying: Check that nginx is correctly proxying requests to port 18789 and that OpenClaw is running
• Messages not arriving: Confirm the messages webhook subscription is active, not just saved
• Token expiry: Always use a system user permanent token, not a temporary developer token
• Number already on WhatsApp: The phone number must be fully removed from regular WhatsApp before registering with the API

What’s Next?

Once connected, your WhatsApp AI assistant via OpenClaw will respond to incoming messages using your configured AI provider. You can set response personas, add memory context, and configure automated routing rules in the OpenClaw config.

Need help navigating the Meta verification process and webhook configuration? Our channel setup service handles the entire WhatsApp Business API registration for you.