kapso-whatsapp

Integrates WhatsApp Business messaging through Kapso APIs, SDK, CLI, webhooks, and MCP servers.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/lurodrisilva/personal-skills --skill kapso-whatsapp-lurodrisilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kapso-whatsapp
Source: https://github.com/lurodrisilva/personal-skills/tree/main/ai/kapso-whatsapp
Command: npx skills add https://github.com/lurodrisilva/personal-skills --skill kapso-whatsapp-lurodrisilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @kapso/whatsapp-cloud-api, @kapso/cli, @kapso/workflows, jq, curl, and includes scripts (resource) components.

What problem does it solve? Building WhatsApp integrations requires navigating Meta's Cloud API rules, the 24-hour messaging window, template approvals, webhook signature verification, and rate limits. This Skill encodes the complete Kapso platform playbook so an AI agent can send messages, onboard numbers, verify webhooks, and run workflows without re-deriving these constraints from documentation. ## Core Features & Use Cases - Messaging & Templates: Send text, media, interactive, and template messages via the @kapso/whatsapp-cloud-api SDK or the Meta-mirror REST API, with correct handling of the 24-hour window, template lifecycle, and business-scoped user IDs (BSUID). - Webhooks & Events: Register project or per-number webhooks, verify HMAC-SHA256 signatures on raw bodies, handle buffering/ordering/retries/auto-pause, and dedupe on X-Idempotency-Key. - Workflows, Functions & Agents: Build lock-versioned workflows with kapso pull/build/push, deploy Cloudflare-Worker functions, and wire agents through Project MCP, Docs MCP, the CLI, Chat SDK, OpenClaw, Hermes, or n8n. - Use Case: A SaaS platform needs to onboard customer WhatsApp numbers and send order notifications. The Skill guides creating customers and setup links, syncing approved templates, sending messages within rate limits, and auditing webhooks with the read-only triage scripts in tools/. ## Quick Start Ask the agent to send a WhatsApp template message through Kapso using the KAPSO_API_KEY environment variable and verify the webhook endpoint signature handling.

Frequently Asked Questions about kapso-whatsapp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send a WhatsApp message with the Kapso API?▼

Send WhatsApp messages by calling POST https://api.kapso.ai/meta/whatsapp/v24.0/{phone_number_id}/messages with the X-API-Key header, or use the WhatsAppClient from @kapso/whatsapp-cloud-api with baseUrl and kapsoApiKey. Free-form messages require an open 24-hour window; otherwise send an approved template.

How do I verify Kapso webhook signatures in Node.js?▼

Verify Kapso webhooks by computing HMAC-SHA256 over the raw request body (use express.raw, not a re-serialized JSON body) and comparing it to the X-Webhook-Signature header with a length-guarded crypto.timingSafeEqual. Return 200 within 10 seconds and dedupe on X-Idempotency-Key.

What is the difference between Kapso Project MCP and Docs MCP?▼

Project MCP at https://api.kapso.ai/mcp operates real project resources with grouped tools like whatsapp_messages and whatsapp_webhooks, including mutating actions that should be human-gated. Docs MCP at https://docs.kapso.ai/mcp is read-only documentation search with no authentication.

Can I test WhatsApp templates in the Kapso sandbox?▼

No, the Kapso sandbox cannot send templates, sync templates, message multiple recipients, or accept BSUID recipients. It supports text and interactive flow testing only; connect a production number before doing template work.

Why does my Kapso webhook keep getting paused?▼

Kapso auto-pauses a webhook when, within a 15-minute window, there are at least 20 deliveries, at least 10 failures, and an 85% or higher failure rate. Common causes are slow handlers exceeding the 10-second ack limit or signature verification returning 500 instead of 401; re-enable from Integrations → Webhooks after fixing the endpoint.

How do I update a Kapso workflow without losing nodes?▼

Update workflows with PATCH /workflows/{id} including the latest lock_version, and remember nodes and edges are replacement sets when present, so omitted collections stay unchanged but partial node lists delete the rest. Prefer the CLI loop: kapso pull, edit, kapso build, kapso push --dry-run, then kapso push.