integrate-whatsapp
by gokapsoThe integrate-whatsapp skill helps you connect WhatsApp with Kapso end to end: install the skill, onboard customers, detect connections, handle webhooks, and send messages, templates, media, and Flows. It is a practical integrate-whatsapp guide for backend development and multi-tenant integrations.
This skill scores 82/100, which means it is a solid listing candidate for directory users. The repository shows a real end-to-end WhatsApp integration workflow with clear triggers, operational steps, and substantial reference material, so an agent can likely install it and execute it with less guesswork than a generic prompt.
- Explicitly triggerable for WhatsApp onboarding, webhooks, messaging, templates, media, and Flows in the skill description.
- Strong operational depth: valid frontmatter, 15k+ body, 9 H2s, 17 H3s, code fences, and 52 scripts plus 11 reference files.
- Good progressive disclosure across setup links, connection detection, API references, webhook payloads, and template/flow examples.
- No install command is provided in SKILL.md, so users may need to infer setup steps from npm and CLI references.
- The repo is broad and complex; agents may still need to choose between CLI and direct API paths, especially for multi-tenant customer onboarding.
Overview of integrate-whatsapp skill
What integrate-whatsapp does
The integrate-whatsapp skill helps you connect WhatsApp to a product with Kapso, from customer onboarding to message delivery. It is most useful when you need an integrate-whatsapp guide that covers setup links, connection detection, webhooks, template sending, media, and WhatsApp Flows in one workflow.
Best-fit use cases
Use this integrate-whatsapp skill for backend systems that must:
- onboard customers into their own WhatsApp Business account
- detect when a number becomes connected
- receive message and conversation events through webhooks
- send outbound messages, templates, and media
- manage Flows endpoints, encryption, and publish steps
Why this skill is worth installing
The main advantage is workflow completeness. The repository gives you practical paths for both CLI-first and API-first integration, which matters if your environment is still changing or if you need to support multiple tenants. If you are deciding on an integrate-whatsapp install, this skill is stronger than a generic prompt because it includes the moving parts that usually block production work: IDs, webhook routing, setup-link lifecycle, and the distinction between project-level and phone-number-level operations.
How to Use integrate-whatsapp skill
Install and confirm context
Install with npx skills add gokapso/agent-skills --skill integrate-whatsapp. Before asking for implementation help, confirm the repository context in your project and read SKILL.md first. Then inspect references/getting-started.md, references/platform-api-reference.md, references/webhooks-overview.md, and references/setup-links.md because they explain the actual integration path better than a quick skim of assets.
Turn a rough goal into a usable prompt
For best integrate-whatsapp usage, describe:
- whether you are using Kapso CLI or direct API calls
- whether the app is multi-tenant or single-number
- which step you are stuck on: onboarding, connection detection, webhook handling, sending, or Flows
- the exact objects you already have, such as
customer_id,phone_number_id,business_account_id, or webhook secret
A strong prompt looks like:
Implement WhatsApp onboarding for a multi-tenant SaaS. I already have
customer_id, need a setup-link flow, webhook confirmation forwhatsapp.phone_number.created, and a send-message path usingphone_number_id.
Files and workflows to read first
Start with the files that shape implementation choices:
references/getting-started.mdfor end-to-end flowreferences/detecting-whatsapp-connection.mdfor connection events and redirect handlingreferences/webhooks-reference.mdandreferences/webhooks-overview.mdfor event delivery rules and signature verificationreferences/templates-reference.mdif you send templates or mediareferences/whatsapp-flows-spec.mdplusassets/sample-flow.jsonif you need Flows
Useful assets to review early:
assets/webhooks-example.jsonassets/dynamic-flow.jsonassets/send-template-order-status-update.jsonassets/send-interactive-buttons.json
Practical usage tips
Prefer the CLI when you are exploring project state, customers, or numbers, and use raw API calls when embedding the integration into your own backend. Do not mix up setup-link onboarding with message sending: onboarding creates or resolves the connected number, while sending requires the correct phone_number_id. That distinction is central to successful integrate-whatsapp usage and avoids most integration errors.
integrate-whatsapp skill FAQ
Is this only for Backend Development?
Yes, this integrate-whatsapp for Backend Development skill is primarily for backend work. It fits server-side onboarding, webhook processing, API authentication, and message orchestration. It is not a UI-copy skill and not a pure prompt template for marketing content.
How is this different from a normal prompt?
A normal prompt often describes WhatsApp integration vaguely. The integrate-whatsapp skill is more useful because it reflects the actual integration surface: setup links, webhook events, number resolution, and WhatsApp Flows. That reduces guesswork when you need something deployable rather than illustrative.
Do I need Kapso CLI to use it?
No, but the CLI is the preferred path in the skill because it helps with project selection, setup, and number discovery. If your team cannot use CLI tooling, the references still support direct API calls through X-API-Key.
When should I not use integrate-whatsapp?
Skip this skill if you only want a high-level WhatsApp product overview, or if you are integrating with a completely different provider and do not plan to use Kapso’s platform APIs. It is also a poor fit if you only need a one-off message example without onboarding or webhooks.
How to Improve integrate-whatsapp skill
Give the skill the right starting state
The best improvements come from supplying real integration state: current project ID, whether a customer already exists, the webhook endpoint you own, and the message type you need to send. This makes integrate-whatsapp install outcomes more actionable because the skill can reason about where your flow begins instead of restating setup from zero.
Be explicit about the failure mode
If you want better results, name the blocker:
- “setup link opens but no phone number is created”
- “webhook arrives but signature verification fails”
- “template send works in test but not in production”
- “I have the wrong
phone_number_id”
That kind of input produces more useful integrate-whatsapp usage guidance than asking for a generic integration plan.
Use the right artifacts for iteration
If your first output is incomplete, iterate with one of these:
- the webhook payload you received
- the template JSON you want to send
- the Flow JSON you want to publish
- the command output from
kapso status,kapso whatsapp numbers list, or your API response
For integrate-whatsapp guide work, these artifacts matter more than broad requirements because they let you correct IDs, event names, redirect handling, and payload shape quickly.
Watch the common production mistakes
The most common failure modes are using the wrong identifier, subscribing to the wrong webhook type, or assuming setup completion automatically means message readiness. Improve the skill’s output by stating whether you need project webhooks or phone-number webhooks, whether you are using Kapso or Meta proxy endpoints, and whether your app must support coexistence or dedicated mode.