WhatsApp Business Cloud API

This connector uses Meta's WhatsApp Business Cloud API (Graph API v22.0).

Setup:

1. Go to https://developers.facebook.com/ → create or pick an App → add the WhatsApp product.
2. Under WhatsApp → API Setup, you find: a temporary 24h access token (for testing), the test Phone Number ID, and the WhatsApp Business Account ID (WABA ID).
3. For production, generate a permanent System User access token at Meta Business Suite → Business Settings → System Users → add user → assign the WhatsApp Business Account → generate token with whatsapp_business_messaging and whatsapp_business_management permissions.
4. Paste the token as WHATSAPP_ACCESS_TOKEN and the WABA ID as WHATSAPP_BUSINESS_ACCOUNT_ID.

Phone Number ID: every business account has one or more sending phone numbers, each identified by a phoneNumberId. Call whatsapp_list_phone_numbers once after setup to discover the IDs available on your WABA. Every send tool requires phoneNumberId — the connector does NOT auto-resolve a default, you must pass it explicitly on each call.

Recipient format: the to field is the recipient's phone number in international format without the + sign, country code first (e.g. 15551234567 for the US, 4915151234567 for Germany).

Templates vs free-form text:

• Outside the 24-hour customer service window, you can ONLY send pre-approved template messages (whatsapp_send_template_message). Templates must be created and approved in Meta Business Suite before they can be used.
• Inside the 24-hour window (i.e. the user has messaged your number in the last 24h), you can send free-form text, media, interactive messages, location, etc.

Sending media (image / audio / voice / video / document): WhatsApp accepts media in two ways:

1. By public URL (recommended on AnythingMCP): use the per-type tools (whatsapp_send_image, whatsapp_send_audio, whatsapp_send_video, whatsapp_send_document) and pass link = a publicly accessible HTTPS URL. The URL must be reachable from Meta's servers and respect WhatsApp size limits (image 5 MB, audio/voice 16 MB, video 16 MB, document 100 MB).
2. By uploaded media ID: upload a binary first to /PHONE_NUMBER_ID/media (multipart/form-data with a real file) to obtain a media_id, then reference it in a send call. AnythingMCP's REST engine does not currently orchestrate the binary upload step in a single tool — for this flow either pre-upload via your own infrastructure and pass the resulting mediaId to the per-type send tools, or stick to the URL-based path above.

Voice notes specifically: use whatsapp_send_audio with an OGG-Opus or AMR file. WhatsApp renders OGG-Opus as a true voice message (waveform + play button) in the client.

Cost / quota: WhatsApp pricing is per conversation (24-hour session), not per message. Marketing, utility and authentication conversations are priced differently per country — see https://developers.facebook.com/docs/whatsapp/pricing/.

Inbound messages (webhook): this connector does NOT receive inbound messages. Meta delivers them via a webhook you must host yourself; AnythingMCP's current architecture is request/response only. If you need a chatbot that replies to user messages, host a webhook receiver separately and use this connector for the outbound side. Use whatsapp_mark_message_as_read to send read receipts for messages your webhook has processed.