← Back to Skills Marketplace
24521
Downloads
61
Stars
0
Active Installs
17
Versions
Install in OpenClaw
/install whatsapp-business
Description
WhatsApp Business API integration with managed OAuth. Send messages, manage templates, and handle conversations. Use this skill when users want to interact with WhatsApp Business. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a WhatsApp Business connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a WhatsApp Business action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with WhatsApp Business examples; they add no WhatsApp Business capability - WhatsApp Business is not an event source, a trigger cannot read WhatsApp Business data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Before installing, understand that this skill can send real WhatsApp messages to real people and may incur business, privacy, or reputation impact. Use it only with the intended WhatsApp Business account, confirm every recipient and write action, avoid broad or persistent automation unless you explicitly need it, and do not expose Maton or provider credentials in files, logs, headers, or prompts.
Capability Assessment
Credentials
The skill requires network access, a Maton account, OAuth/browser authorization, and Bash use, which are proportionate for a managed API integration. Raw HTTP with a long-lived API key is documented only as a last resort with handling cautions.
Install Mechanism
Installation is disclosed and uses pinned Maton CLI/package versions or a pinned Homebrew install; no hidden install scripts or embedded executable payloads were present.
Instruction Scope
The skill repeatedly narrows agent behavior to documented WhatsApp Business endpoints, defaults to read/list operations, requires explicit approval for writes, connection creation, hosted functions, trigger destinations, and local event execution, and treats third-party content as untrusted data.
Persistence & Privilege
OAuth tokens are stored in the OS credential store and Maton functions/triggers/destinations can persist beyond a single session, but this is disclosed with approval, least-privilege, deletion, and credential-handling guidance.
Purpose & Capability
The documented capabilities fit the stated purpose: connecting a WhatsApp Business account, reading/listing account resources, sending messages, managing templates/media/profile details, and optionally using Maton functions/triggers for user-approved automation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install whatsapp-business - After installation, invoke the skill by name or use
/whatsapp-business - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.9
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.8
- Updated WhatsApp Business API version in usage examples from v21.0 to v25.0 for compatibility with the latest API.
- Removed the redundant skill-card.md file for clarity and maintenance.
- No other functional or documentation changes were introduced.
v1.2.7
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.6
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.5
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.4
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.3
Harden every multipart upload example: the assembled request body now goes to an owner-only file created with umask 077 and mktemp, removed by a trap on any exit, instead of a predictable shared /tmp path that could be pre-created by another user and left behind holding a copy of the uploaded file
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.1
- Removed the sample file skill-card.md.
- No other functional or documentation changes in this patch.
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.4
- Changed all endpoint URLs from *.maton.ai/gateway and *.maton.ai/ctrl to *.maton.ai/api.
- Updated examples and documentation to use the new https://api.maton.ai base URL for WhatsApp Business API and connection management.
- Added a Security & Permissions section clarifying access scope and user approval requirements for write operations.
- Removed LICENSE.txt file from the project.
v1.0.3
- Added metadata specifying required environment variable: MATON_API_KEY.
- Included emoji indicator in the metadata for identification.
- No changes to code or core functionality.
v1.0.2
- Documentation formatting corrections in SKILL.md for improved readability.
- No functional or API changes in this version.
v1.0.1
- Added a reference to the api-gateway skill in the description for interactions with other third party apps.
- Updated all Quick Start and connection management examples to use Python scripts instead of curl.
- Changed environment variable usage in documentation from `YOUR_API_KEY` to `$MATON_API_KEY` for improved consistency.
- Minor clarity and style adjustments throughout documentation.
v1.0.0
Initial release of WhatsApp Business API integration.
- Provides managed OAuth authentication via Maton.
- Supports sending messages (text, templates, media, location, contacts, interactive types).
- Enables message template management.
- Allows connection management (create, list, delete, specify via header).
- Proxy gateway to WhatsApp Business API using Maton API key for authentication.
- Includes example cURL commands and detailed usage instructions.
Metadata
Frequently Asked Questions
What is WhatsApp Business?
WhatsApp Business API integration with managed OAuth. Send messages, manage templates, and handle conversations. Use this skill when users want to interact with WhatsApp Business. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a WhatsApp Business connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a WhatsApp Business action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with WhatsApp Business examples; they add no WhatsApp Business capability - WhatsApp Business is not an event source, a trigger cannot read WhatsApp Business data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 24521 downloads so far.
How do I install WhatsApp Business?
Run "/install whatsapp-business" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is WhatsApp Business free?
Yes, WhatsApp Business is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does WhatsApp Business support?
WhatsApp Business is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created WhatsApp Business?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.9.
More Skills