OpenClaw WhatsApp & Messaging Integration

How OpenClaw Connects to Messaging Apps (Via Skills)

The current architecture uses channel adapters and plugins rather than a generic Skill for every messaging app. OpenClaw's Gateway normalizes incoming messages, routes them to an agent session, and sends replies through the selected channel. Skills may help an agent perform tasks after a message arrives, but installing an unrelated Skill does not configure WhatsApp, WeChat, or iMessage transport.

This distinction matters during troubleshooting. Channel credentials live under channel-specific configuration and state, while Skills are task assets that can run code or call tools. Audit both, but do not treat them as the same layer.

Install the WhatsApp Skill: Step-by-Step

There is no official WhatsApp Skill required for the documented setup. WhatsApp is install-on-demand as an external channel plugin and currently uses a QR-based WhatsApp Web connection. Configure the access policy, log in, start the Gateway, and approve the first sender if pairing is enabled:

{
 channels: {
 whatsapp: {
 dmPolicy: "pairing",
 allowFrom: ["+15551234567"],
 groupPolicy: "allowlist",
 groupAllowFrom: ["+15551234567"]
 }
 }
}

openclaw channels login --channel whatsapp
openclaw gateway
openclaw pairing list whatsapp
openclaw pairing approve whatsapp <CODE>

Use a direct QR handoff on remote hosts because terminal captures and relayed screenshots can expire. A dedicated WhatsApp number is the cleanest operational pattern; a personal-number setup is supported but has more self-chat and identity ambiguity.

Connecting WeChat to OpenClaw

WeChat support comes from Tencent's external @tencent-weixin/openclaw-weixin package, not OpenClaw core. Install the plugin, enable it, restart the Gateway, and complete QR login on the Gateway host:

openclaw plugins install "@tencent-weixin/openclaw-weixin"
openclaw config set plugins.entries.openclaw-weixin.enabled true
openclaw gateway restart
openclaw channels login --channel openclaw-weixin

The current plugin advertises direct chats and media, not group chats. It also has version compatibility requirements, so check the plugin line against your OpenClaw version before assuming a login failure is a credential problem.

iMessage Integration on macOS

iMessage requires access to a signed-in macOS Messages environment. The current path uses imsg, a message database path, and macOS permissions such as Full Disk Access. For isolation, use a dedicated macOS user and Apple ID when possible.

{
 channels: {
 imessage: {
 enabled: true,
 cliPath: "/opt/homebrew/bin/imsg",
 dbPath: "/Users/bot/Library/Messages/chat.db",
 includeAttachments: true
 }
 }
}

A Linux Gateway can reach a separate Mac through an SSH wrapper, but the iMessage identity and imsg process still live on macOS. iOS can act as an OpenClaw node; it is not the documented host for the iMessage channel bridge.

Security Considerations Before Linking Personal Messaging

Messaging archives may contain identity details, private files, account recovery links, and instructions from people who never agreed to interact with an AI agent. Before connecting an account:

• use a dedicated messaging identity where practical;
• isolate DMs by sender with session.dmScope if multiple people can reach the agent;
• restrict group IDs and sender IDs separately;
• limit tool permissions for channel-originated sessions;
• protect local credential and session directories;
• require approval for irreversible actions and outbound messages;
• review attachment roots and media size limits.

Pairing approves a sender; it does not make every message trustworthy. Prompt injection can arrive through ordinary text, files, and links from an approved contact.

What Your Agent Can and Can't Do via Messaging Channels

All supported channels carry text, but media, reactions, edits, threads, and group behavior vary. WhatsApp is based on a WhatsApp Web session rather than a Twilio channel. WeChat's current external plugin does not advertise groups. iMessage depends on macOS database and automation permissions.

The agent can only perform actions exposed by the channel adapter and its effective tool policy. It should not be described as having universal access to a person's phone, every historical message, or every messaging feature. If you need several channel identities routed to separate personas, the OpenClaw multi-agent configuration guide explains per-agent workspaces and bindings.

In Verdent

Messaging integrations are optimized for reaching an assistant from familiar chat apps. Verdent addresses a different job: planning, implementing, and reviewing software changes in a development environment. Use it as a separate coding workspace rather than presenting it as an OpenClaw channel or Skill.

Sources: OpenClaw WhatsApp documentation, WeChat plugin guide, iMessage documentation, and channel overview.