by @gora050
Whatsapp integration. Manage Chats, Users, Groups, Contacts, Statuses. Use when the user wants to interact with Whatsapp data.
clawhub install whatsapp-integrationπ About This Skill
name: whatsapp description: | Whatsapp integration. Manage Chats, Users, Groups, Contacts, Statuses. Use when the user wants to interact with Whatsapp data. compatibility: Requires network access and a valid Membrane account (Free tier supported). license: MIT homepage: https://getmembrane.com repository: https://github.com/membranedev/application-skills metadata: author: membrane version: "1.0" categories: "Communication"
WhatsApp is a messaging application that allows users to send text, voice messages, make voice and video calls, and share images, documents, user locations, and other content. It's primarily used by individuals for personal communication but also has business solutions for customer support and marketing.
Official docs: https://developers.facebook.com/docs/whatsapp
Whatsapp Overview
Use action names and parameters as needed.
Working with Whatsapp
This skill uses the Membrane CLI to interact with Whatsapp. Membrane handles authentication and credentials refresh automatically β so you can focus on the integration logic rather than auth plumbing.
Install the CLI
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli@latest
Authentication
membrane login --tenant --clientName=
This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.
Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:
membrane login complete
Add --json to any command for machine-readable JSON output.
Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness
Connecting to Whatsapp
Use membrane connection ensure to find or create a connection by app URL or domain:
membrane connection ensure "https://web.whatsapp.com" --json
This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.
If the returned connection has state: "READY", skip to Step 2.
#### 1b. Wait for the connection to be ready
If the connection is in BUILDING state, poll until it's ready:
npx @membranehq/cli connection get --wait --json
The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.
The resulting state tells you what to do next:
READY β connection is fully set up. Skip to Step 2.CLIENT_ACTION_REQUIRED β the user or agent needs to do something. The clientAction object describes the required action:clientAction.type β the kind of action needed:
- "connect" β user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
- "provide-input" β more information is needed (e.g. which app to connect to).
- clientAction.description β human-readable explanation of what's needed.
- clientAction.uiUrl (optional) β URL to a pre-built UI where the user can complete the action. Show this to the user when present.
- clientAction.agentInstructions (optional) β instructions for the AI agent on how to proceed programmatically. After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get to check if the state moved to READY.
CONFIGURATION_ERROR or SETUP_FAILED β something went wrong. Check the error field for details.Searching for actions
Search using a natural language description of what you want to do:
membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json
You should always search for actions in the context of a specific connection.
Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).
Popular actions
| Name | Key | Description | | --- | --- | --- | | Send Sticker Message | send-sticker-message | Send a sticker message to a WhatsApp user. | | Update Business Profile | update-business-profile | Update the WhatsApp Business Profile information. | | Get Business Profile | get-business-profile | Retrieve the WhatsApp Business Profile information including about text, address, description, email, and websites. | | Mark Message as Read | mark-message-as-read | Mark a received message as read. | | Send Reaction | send-reaction | Send a reaction emoji to a specific message. | | Send Contacts Message | send-contacts-message | Send one or more contact cards (vCards) to a WhatsApp user. | | Send Location Message | send-location-message | Send a location message with coordinates and optional name/address to a WhatsApp user. | | Send Interactive List Message | send-interactive-list-message | Send an interactive message with a list menu containing up to 10 selectable options organized in sections. | | Send Interactive Buttons Message | send-interactive-buttons-message | Send an interactive message with up to 3 reply buttons for quick user responses. | | Send Audio Message | send-audio-message | Send an audio message to a WhatsApp user. | | Send Video Message | send-video-message | Send a video message to a WhatsApp user. | | Send Document Message | send-document-message | Send a document file to a WhatsApp user. | | Send Image Message | send-image-message | Send an image message to a WhatsApp user. | | Send Template Message | send-template-message | Send a pre-approved template message to a WhatsApp user. | | Send Text Message | send-text-message | Send a text message to a WhatsApp user |
Running actions
membrane action run --connectionId=CONNECTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID --input '{"key": "value"}' --json
The result is in the output field of the response.
Proxy requests
When the available actions don't cover your use case, you can send requests directly to the Whatsapp API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers β including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|------|-------------|
| -X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
| -H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
| -d, --data | Request body (string) |
| --json | Shorthand to send a JSON body and set Content-Type: application/json |
| --rawData | Send the body as-is without any processing |
| --query | Query-string parameter (repeatable), e.g. --query "limit=10" |
| --pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
Best practices
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.π Tips & Best Practices
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.