Menu
Add WhatsApp Business Cloud API channel via Chat SDK. Official Meta API.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | add-whatsapp-cloud |
| description | Add WhatsApp Business Cloud API channel via Chat SDK. Official Meta API. |
Connect NanoClaw to WhatsApp via the official Meta WhatsApp Business Cloud API.
NanoClaw doesn't ship channels in trunk. This skill copies the WhatsApp Cloud adapter in from the channels branch.
Skip to Credentials if all of these are already in place:
src/channels/whatsapp-cloud.ts existssrc/channels/whatsapp-cloud-registration.test.ts existssrc/channels/index.ts contains import './whatsapp-cloud.js';@chat-adapter/whatsapp is listed in package.json dependenciesOtherwise continue. Every step below is safe to re-run.
git fetch origin channels
git show origin/channels:src/channels/whatsapp-cloud.ts > src/channels/whatsapp-cloud.ts
git show origin/channels:src/channels/whatsapp-cloud-registration.test.ts > src/channels/whatsapp-cloud-registration.test.ts
Append to src/channels/index.ts (skip if the line is already present):
import './whatsapp-cloud.js';
pnpm install @chat-adapter/whatsapp@4.29.0
pnpm run build
pnpm exec vitest run src/channels/whatsapp-cloud-registration.test.ts
Both must be clean before proceeding. whatsapp-cloud-registration.test.ts is the one integration test: it imports the real channel barrel and asserts the registry contains whatsapp-cloud. It goes red if the import './whatsapp-cloud.js'; line is deleted or drifts, if the barrel fails to evaluate, or if @chat-adapter/whatsapp isn't installed (the import throws) — so it also implicitly verifies the dependency from step 4. The adapter also calls core's createChatSdkBridge(...); that typed core-API consumption is guarded by pnpm run build.
End-to-end message delivery against a real WhatsApp Business number is verified manually once the service is running — see Next Steps and the webhook setup above.
whatsapp_business_messaging permission.https://your-domain/webhook/whatsapp.messages.Add to .env:
WHATSAPP_ACCESS_TOKEN=your-system-user-access-token
WHATSAPP_PHONE_NUMBER_ID=your-phone-number-id
WHATSAPP_APP_SECRET=your-app-secret
WHATSAPP_VERIFY_TOKEN=your-verify-token
Sync to container: mkdir -p data/env && cp .env data/env/env
If you're in the middle of /setup, return to the setup flow now.
Otherwise, run /manage-channels to wire this channel to an agent group.
whatsapp-cloudAdd persistent graph-based memory via mnemon. Agents recall past context before responding and remember insights after each turn.
Use OpenCode as an agent provider. OpenRouter, OpenAI, Google, DeepSeek, etc. via OpenCode config — not the Anthropic Agent SDK. Per group via `ncl groups config update --provider opencode`; host passes OPENCODE_* and XDG mount when spawning containers.
Configure which host directories agent containers can access. View, add, or remove mount allowlist entries. Triggers on "mounts", "mount allowlist", "agent access to directories", "container mounts".
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Distill a reusable skill from anything — a directory, a URL, pasted notes, or what you just did together — or refine an existing skill with new learnings. Use when the user says '/learn', 'learn this', 'turn this into a skill', 'capture this workflow', 'make a skill from <source>', or 'improve/update the <name> skill'. Produces or updates a .claude/skills/<name>/SKILL.md authored to NanoClaw's skill guidelines. (This CREATES or REFINES a skill from a source; it does not install existing skills from a registry.)
Add Discord bot channel integration via Chat SDK.