🔧 Tool: openclaw-kapso-whatsapp

[hasamba@infosec.exchange]

----------------

Tool: openclaw-kapso-whatsapp

Overview

openclaw-kapso-whatsapp provides a production‑oriented bridge that assigns a WhatsApp number to an OpenClaw AI agent by proxying requests through Kapso and the official WhatsApp Cloud API. The project emphasizes a stateless design implemented as two Go binaries: a bridge component that handles incoming events and a CLI/utility component for preflight and control. The bridge relays messages via a session JSONL mechanism: it reads session entries and emits replies, keeping runtime resource usage minimal.

Architecture and Components
• kapso API integration: Uses Kapso as a unified adapter for WhatsApp Cloud endpoints rather than reverse‑engineered WebSocket/Web clients.
• Stateless bridge: No persistent session objects are held in memory; API calls are performed per event which yields near‑zero idle CPU consumption.
• Two Go binaries: separates runtime bridge logic from CLI/management utilities.
• Session JSONL relay: message exchange is handled through JSONL session records; the relay reads these and issues outgoing replies.

Capabilities
• Official API path: avoids detection and ban risks associated with libraries that emulate WhatsApp Web (e.g., Baileys, whatsapp‑web.js).
• Low resource footprint: stateless calls and small Go binaries reduce idle CPU and simplify scaling models where ephemeral processes are acceptable.
• Delivery modes: supports polling by default and describes options to cut latency (for example via network tunneling) to reach sub‑second response times.
• Ancillary features: mentions voice transcription support and a NixOS/home‑manager module for system integration.

Operational considerations and limitations
• Statelessness trades in‑memory conversational state for simplified scaling; preserving multi‑turn context requires external state handling (session JSONL or agent backend).
• Reliance on Kapso and the WhatsApp Cloud API implies dependence on third‑party API quotas, rate limits, and billing models controlled by those services.
• Latency: default polling works with minimal config; lower latency relies on additional delivery modes or tunnel mechanisms.

Use cases
• Embedding a conversational AI agent with a dedicated WhatsApp number for task automation, notifications, or interactive workflows.
• Resource‑constrained deployments that require low idle CPU and simple runtime footprints.

openclaw #kapso #whatsapp_cloud_api #go #voice_transcription

Source: https://github.com/Enriquefft/openclaw-kapso-whatsapp