integrate-whatsapp_skill

This skill guides you through integrating WhatsApp with Kapso, onboarding customers, receiving events via webhooks, and sending templates, messages, and media.
  • JavaScript

24

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill gokapso/agent-skills --skill integrate-whatsapp

  • package.json139 B
  • SKILL.md13.5 KB

Overview

This skill connects WhatsApp to your product using Kapso. It guides onboarding with setup links, detects connections, wires webhooks for events, and sends messages, templates, and media. It also manages WhatsApp Flows including creation, updating, publishing, data endpoints, and encryption.

How this skill works

The skill uses Kapso Platform and Meta proxy endpoints: platform routes for onboarding and phone-number provisioning, and /meta/whatsapp for messaging, templates, and media. It exposes scripts and an SDK client wrapper to generate setup links, register webhooks, send text/template/interactive messages, upload media, and manage Flow JSON and data endpoints. Webhooks support both project-level lifecycle events and phone-number scoped WhatsApp message/conversation events with signature verification and buffering options.

When to use it

  • Onboard customers and provision WhatsApp numbers with setup links and automated flows.
  • Receive real-time WhatsApp messages, delivery updates, and connection lifecycle events via webhooks.
  • Send notifications, template messages, interactive messages, and media through Kapso’s Meta proxy or SDK.
  • Build dynamic, data-driven WhatsApp Flows with external data endpoints and encryption.
  • Manage templates (create/update/check status) and enforce template rules before sending.

Best practices

  • Always discover and store business_account_id (WABA) and phone_number_id before template or send operations.
  • Use project webhooks for connection lifecycle and phone-number webhooks for message/conversation events only.
  • Use payload-version v2 for webhooks and verify signatures on every incoming event.
  • Use NAMED template parameters with examples and include parameter_name at send time for reliability.
  • Enable buffering for high inbound throughput and tune buffer-window and max-buffer-size per traffic patterns.

Example use cases

  • Send order status updates using a NAMED utility template with URL buttons and media headers.
  • Onboard a new customer via a setup link that provisions a US phone number and triggers a project webhook.
  • Create a dynamic WhatsApp Flow that calls a secure data endpoint to render personalized screens and submit orders.
  • Receive inbound messages and conversation events to populate a CRM and start a 24-hour interactive session.
  • Upload images or documents via the media upload script and reference them in template headers at send time.

FAQ

Subscribe to the project webhook whatsapp.phone_number.created or use the success redirect URL query params returned after setup link completion.

Which ID do I use to send messages vs manage templates?

Use phone_number_id to send messages and upload media; use business_account_id (WABA) for template CRUD and status checks.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational