Back to browse
GitHub Repository

Give your OpenClaw AI agent a WhatsApp number. Official Meta Cloud API via Kapso. No ban risk.

199 starsGo

OpenClaw-kapso, Give OpenClaw a stable WhatsApp number (Go, kapso.ai)

by enriquefft·Feb 28, 2026·3 points·1 comment

AI Analysis

●●SolidNiche GemSolve My Problem

Uses official WhatsApp Cloud API instead of reverse-engineering—safe integration with stateless polling.

Strengths
  • Genuine safety advantage: official API eliminates ban risk vs. Baileys/whatsapp-web.js
  • Zero-config polling + Tailscale Funnel options = thoughtful deployment flexibility
Weaknesses
  • Extremely niche: only works with OpenClaw ecosystem (1 user reported, 1 star)
  • Requires Kapso paid API key—adds another dependency and cost to setup
Target Audience

OpenClaw agent developers, teams building conversational AI bots

Similar To

Baileys · whatsapp-web.js

Post Description

Built an OpenClaw plugin that gives your agent a WhatsApp number through the official Cloud API via Kapso). Polling works out of the box, or use Tailscale Funnel for sub-second latency without needing a domain. v0.1.0, I'm the only user so far. Would love any kind of feedback.

Similar Projects

Developer Tools●●Solid

AgenticMail – Email, SMS, and multi-agent coordination for AI agents

Hands-off: each agent gets its own mailbox, phone number, inbox and API key, and the project bundles a local Stalwart mail server in Docker plus Gmail-relay or custom-domain outbound with DKIM/SPF/DMARC. Concrete safety features (outbound scanning to catch API keys/PII) and Google Voice SMS extraction for verification codes are genuinely useful and uncommon together. If you want to prototype agents that actually talk to people/services this is a focused, pragmatic stack — but expect telephony fiddliness and compliance trade-offs in real deployments.

WizardryNiche Gem
agenticmail
213mo ago