observe-whatsapp

An operational diagnostics skill for observing and troubleshooting WhatsApp within Kapso. It targets message delivery investigation, webhook delivery debugging, API error triage, and WhatsApp health checks, making it the go-to when investigating production issues, message failures, or webhook delivery problems. It offers two execution paths: a preferred path through the authenticated Kapso CLI, and a fallback path using bundled Node scripts when the CLI is unavailable or when deeper API-log and webhook-delivery inspection is needed.

For message delivery, the preferred path resolves a display number to its canonical phone_number_id, lists recent messages, inspects a specific message, and inspects the conversation, all via kapso whatsapp commands with JSON output; the fallback uses messages.js, message-details.js, and lookup-conversation.js. Error triage confirms project and number state with kapso status, runs number health, and inspects related templates, falling back to errors.js, api-logs.js, and webhook-deliveries.js. Health checks combine a project overview with per-number health, or fall back to overview.js and whatsapp-health.js. An openapi-explore.mjs script lets you search the OpenAPI spec, look up operations, and inspect schemas such as WebhookDelivery, with Node dependencies installed once via npm i.

Setup expects the Kapso CLI installed and authenticated with kapso login, starting from kapso status to confirm project access and available numbers; the fallback relies on the KAPSO_API_BASE_URL and KAPSO_API_KEY environment variables. The guidance recommends resolving a display phone number to its phone_number_id before deep debugging and keeping the scripts as the fallback. For webhook setup such as creating, updating, or deleting webhooks and signature verification, it points to the integrate-whatsapp skill, while automate-whatsapp covers workflows, agents, and automations. Reference guides for message debugging, triage, and health checks accompany the skill.