integrate-whatsapp

Preferred path: Fallback path: Env vars: Auth header (direct API calls): Install deps (once): Preferred onboarding path (CLI): Fallback onboarding flow (direct API): Detect connection: Recommended Kapso setup-link defaults: Notes: kapso setup and kapso whatsapp numbers new use dedicated plus provisioning by default. Keep phone_number_country_isos , phone_number_area_code , language , and redirect URLs as optional overrides. Platform API base: /platform/v1 Meta proxy base: /meta/whatsapp/v24.0 (messaging, templates, media) Use phone_number_id as the primary WhatsApp identifier Use webhooks to receive: Scope rules: Create a webhook: Common flags for create/update: Test delivery: Always verify signatures. See: Two Meta IDs are needed for different operations: Common commands: Install: Create client: Via SDK: Interactive messages require an active 24-hour session window. For outbound notifications outside the window, use templates. Preferred path: Fallback path: Creation: Send-time: Use Flows to build native WhatsApp forms. Read references/whatsapp-flows-spec.md before editing Flow JSON. Static flows (no data endpoint): Dynamic flows (with data endpoint): Handler signature: Examples: - Kapso CLI installed and authenticated ( kapso login ) - Use kapso status to confirm project access before onboarding or messaging - KAPSO_API_BASE_URL (host only, no /platform/v1 ) - KAPSO_API_KEY -...