skills/observe-whatsapp/SKILL.md
Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message failures, or webhook delivery problems.
npx skillsauth add pcruvinel/antig observe-whatsappInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill for operational diagnostics: message delivery investigation, webhook delivery debugging, error triage, and WhatsApp health checks.
Env vars:
KAPSO_API_BASE_URL (host only, no /platform/v1)KAPSO_API_KEYnode scripts/messages.js --phone-number-id <id>node scripts/message-details.js --message-id <id>node scripts/lookup-conversation.js --phone-number <e164>node scripts/errors.jsnode scripts/api-logs.jsnode scripts/webhook-deliveries.jsnode scripts/overview.jsnode scripts/whatsapp-health.js --phone-number-id <id>| Script | Purpose |
|--------|---------|
| messages.js | List messages |
| message-details.js | Get message details |
| lookup-conversation.js | Find conversation by phone or ID |
| Script | Purpose |
|--------|---------|
| errors.js | List message errors |
| api-logs.js | List external API logs |
| webhook-deliveries.js | List webhook delivery attempts |
| Script | Purpose |
|--------|---------|
| overview.js | Project overview |
| whatsapp-health.js | Phone number health check |
| Script | Purpose |
|--------|---------|
| openapi-explore.mjs | Explore OpenAPI (search/op/schema/where) |
Install deps (once):
npm i
Examples:
node scripts/openapi-explore.mjs --spec platform search "webhook deliveries"
node scripts/openapi-explore.mjs --spec platform op listWebhookDeliveries
node scripts/openapi-explore.mjs --spec platform schema WebhookDelivery
integrate-whatsapp.integrate-whatsapp - Onboarding, webhooks, messaging, templates, flowsautomate-whatsapp - Workflows, agents, and automations[observe-whatsapp file map]|root: .
|.:{package.json,SKILL.md}
|assets:{health-example.json,message-debugging-example.json,triage-example.json}
|references:{health-reference.md,message-debugging-reference.md,triage-reference.md}
|scripts:{api-logs.js,errors.js,lookup-conversation.js,message-details.js,messages.js,openapi-explore.mjs,overview.js,webhook-deliveries.js,whatsapp-health.js}
|scripts/lib/messages:{args.js,kapso-api.js}
|scripts/lib/status:{args.js,kapso-api.js}
|scripts/lib/triage:{args.js,kapso-api.js}
<!-- FILEMAP:END -->tools
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
tools
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
tools
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
tools
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power