Channels: WhatsApp

WhatsApp is a Tier 1 channel. Wayland supports more than one backend: a local bridge that pairs by QR code, and the official WhatsApp Cloud API with an access token and webhook.

Before you start (prerequisites and accounts)

A WhatsApp account for the bridge route, or a WhatsApp Business / Cloud API setup for the API route.
The Wayland desktop app running with a model provider connected.

Create the credentials (on the provider side)

For the Cloud API backend, in the Meta developer console collect:

An Access token for the WhatsApp Business account.
The Phone number ID and the Business account ID.
A Verify token you choose, and the App secret for request signing.

For the local bridge backend, no API credentials are needed. You pair by scanning a QR code with the WhatsApp app, the same way WhatsApp Web links a device.

Connect it in Wayland (Settings > Channels > WhatsApp)

Open Settings > Channels and choose WhatsApp.
Choose the Backend (local bridge or Cloud API).
For the bridge, scan the QR code Wayland shows to pair the device. For the Cloud API, enter the access token, phone number ID, business account ID, verify token, and app secret, then point the Meta webhook at the inbound URL Wayland exposes.
Save.

In the Wayland Core CLI, configure the same channel in your Core channel config: choose the Backend, scan the QR code Core prints (bridge) or supply the Cloud API credentials and point the Meta webhook at the inbound URL Core exposes, then start the channel.

Verify (status goes from idle to connected, send a test message)

After pairing or saving, the status moves from idle to connected. Send a WhatsApp message to the linked number and confirm a reply.

Route to an assistant or team

Set the assistant and default model on the WhatsApp page. Inbound messages route to that assistant.

Troubleshooting

If the bridge drops, re-scan the QR code. For the Cloud API, recheck the verify token and webhook configuration. See Channel Connection Issues.