WhatsApp Business

**Quick judgement** A mature, high-usage WhatsApp Business integration built on the Maton gateway. It exposes most core WhatsApp Business Cloud API capabilities (messages, templates, media, phone numbers, business profiles) with managed OAuth and clear HTTP-based usage. Well-suited as a general WhatsApp Business connector within OpenClaw. **Strengths & advantages** - **Feature-complete messaging**: Text, template, media, location, contacts, interactive buttons/lists, and read receipts are all supported via straightforward JSON payloads. - **Managed OAuth & connection model**: Offloads the complexity of Meta/WhatsApp authorization to Maton; supports multiple connections and explicit selection via `Maton-Connection` header. - **Good developer ergonomics**: Clear base URL scheme, environment-variable auth, concrete Python/JavaScript examples, and detailed request/response samples. - **Operational clarity**: Error codes, rate limits (10 req/sec), troubleshooting tips for API keys and app names, and documented WhatsApp-specific error codes. **Key risks & limitations** - **External dependency**: Relies on Maton’s gateway availability and policies in addition to WhatsApp’s own reliability and limits. Any outage or change upstream affects this skill. - **Compliance & data handling**: WhatsApp inherently carries PII (phone numbers, message content). The docs do not detail data retention, regional hosting, or compliance guarantees (e.g., GDPR, HIPAA). Use in regulated environments requires additional due diligence. - **Rate limits & scaling**: The documented 10 req/sec per account rate limit may constrain very high-throughput use cases without careful batching or account sharding. **Recommended scenarios** - You need **production-grade WhatsApp Business messaging** (support, notifications, or marketing) without managing Meta OAuth flows or raw Graph API calls yourself. - You are building **multi-step workflows or chatbots** in OpenClaw that require rich WhatsApp interactions (buttons, lists, media) and want a single, well-documented integration point. - You want to **manage templates and business profiles programmatically** alongside messaging within the same integration. **Less ideal if** - You must avoid third-party gateways for **compliance or data residency** reasons and need direct, in-house integration with Meta’s APIs. - You require hard guarantees on **throughput, latency, or regional hosting**, which are not specified in the current documentation.