---
name: oo-whatsapp
description: "WhatsApp (whatsapp.com). Use this skill for ANY WhatsApp request — reading, creating, updating, and deleting data. Whenever a task involves WhatsApp, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
  title: "WhatsApp"
  author: "OOMOL"
  version: "1.0.5"
  services: ["whatsapp"]
  icon: "https://static.oomol.com/logo/third-party/whatsapp.svg"
---

# WhatsApp

Operate **WhatsApp** through your OOMOL-connected account. This skill calls the `whatsapp` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.

## Running an action

Assume the user has already installed the oo CLI, signed in, and connected WhatsApp. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.

**1. Inspect the contract** to get the authoritative input/output schema before building a payload:

```bash
oo connector schema "whatsapp" --action "<action_name>"
```

**2. Run the action** with a JSON payload that matches the input schema:

```bash
oo connector run "whatsapp" --action "<action_name>" --data '<json>' --json
```

- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.

Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.

## Available actions

- `create_message_template` — Create a new WhatsApp message template for a WABA. [write]
- `delete_message_template` — Delete all message template variants that share the same name. [destructive]
- `get_business_profile` — Get the business profile configured for a WhatsApp Business phone number.
- `get_media_info` — Get metadata and a short-lived download URL for uploaded media.
- `get_message_analytics` — Get sent and delivered message counts for a WhatsApp Business Account over a time window.
- `get_message_templates` — List message templates for a WhatsApp Business Account.
- `get_phone_number` — Get metadata for a specific WhatsApp Business phone number.
- `get_phone_numbers` — List phone numbers for a WhatsApp Business Account.
- `get_pricing_analytics` — Get per-message volume and cost for a WhatsApp Business Account over a time window, optionally broken down by phone number, country, pricing category, pricing type, or tier.
- `get_template_analytics` — Get daily sent, delivered, read, click, and cost metrics for up to ten message templates. Template analytics must be enabled on the WABA first, and Meta keeps 90 days of history.
- `get_template_status` — Get status details for a specific message template.
- `send_contacts` — Send one or more contacts to a WhatsApp user. [write]
- `send_interactive_buttons` — Send an interactive reply-button message. [write]
- `send_interactive_list` — Send an interactive list message with sections and rows. [write]
- `send_location` — Send a location message to a WhatsApp user. [write]
- `send_media` — Send a media message by public URL. [write]
- `send_media_by_id` — Send previously uploaded media by Meta media ID. [write]
- `send_message` — Send a text message to a WhatsApp user. [write]
- `send_template_message` — Send an approved WhatsApp template message. [write]
- `upload_media` — Upload media to Meta and return the resulting media record. [write]

## Safety

- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change WhatsApp state — confirm the exact payload and effect with the user before running.**
- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**

## First-time setup

These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):

  ```bash
  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  ```

  ```powershell
  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  ```

- **Not signed in / authentication error** — sign in to your OOMOL account once:

  ```bash
  oo auth login
  ```

- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — WhatsApp is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  ```text
  https://console.oomol.com/connections/whatsapp
  ```

- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

## Resources

- WhatsApp homepage: https://www.whatsapp.com
- API documentation: https://developers.facebook.com/docs/whatsapp/cloud-api/get-started
