Claude Connectors for WhatsApp: Options and Limits

There is no standard Claude connector for WhatsApp through Claude's connector settings. Connecting Claude to WhatsApp requires the WhatsApp Business API, which has its own account requirements, approval process, and messaging rules. For teams that use WhatsApp for customer communication, that path is available but not trivial to set up. For personal WhatsApp accounts, the options are more limited. Tools like fenbs record agreed follow-up work outside individual message threads so nothing falls through when the conversation moves on.

Check Claude's connector settings for any current WhatsApp option. If nothing appears, the sections below explain the main paths and what to verify before choosing one.

Why a direct WhatsApp connector is not straightforward

WhatsApp does not provide a general-purpose read API for personal accounts. Unlike Telegram's Bot API, there is no officially supported way to connect a third-party app to a personal WhatsApp account and read or send messages programmatically. Unofficial methods exist but carry risk: they violate WhatsApp's terms of service and can result in account bans.

The official path for business use is the WhatsApp Business API (also called the WhatsApp Business Platform), managed through Meta. This gives verified businesses the ability to send and receive messages programmatically, but it requires a verified business account, a Meta Business account, and approval from Meta before it can be used.

The WhatsApp Business API route

The WhatsApp Business API lets businesses send messages to WhatsApp users who have opted in to receive them. An AI like Claude can use this API through an MCP server or integration to read incoming messages and send approved responses.

Key requirements before you can use this path:

• A Meta Business account with a verified business.
• A phone number dedicated to WhatsApp Business — not a personal number.
• Approval from Meta for the WhatsApp Business API access.
• Compliance with WhatsApp's messaging policy: only users who have opted in can receive messages, and certain message types require pre-approved templates.

For the current requirements and setup steps, see Meta's developer documentation↗ (opens in a new tab). Requirements and available features change as Meta updates the platform.

Business verification typically takes several days and requires submitting business documentation to Meta. Plan for that lead time before a production launch. The phone number you register for WhatsApp Business API is dedicated to that purpose — it cannot simultaneously be used as a regular WhatsApp account on a phone, so use a number set aside specifically for business messaging.

Messaging restrictions to check

WhatsApp Business API messages are not free-form. Meta distinguishes between utility messages, authentication messages, and marketing messages, each with different rules and costs. Messages sent outside a 24-hour customer service window require pre-approved templates.

This means an AI workflow that replies to incoming customer messages within the 24-hour window is different from one that initiates contact or sends campaign messages. Review which message category your workflow falls into before building the integration.

What Claude cannot do on personal WhatsApp

Claude cannot read or send messages on a personal WhatsApp account through any officially supported connection. Personal WhatsApp does not expose an API for third-party access. Any tool that claims to connect Claude to a personal WhatsApp account is using unofficial methods that risk account suspension.

For personal communication workflows that benefit from AI assistance, consider whether a different messaging platform with better AI integration — or a separate channel for AI-assisted work — would meet the need without the compliance risk.

Telegram's Bot API is designed for third-party access and provides a legitimate route to connect Claude to a messaging channel. If your audience is comfortable with Telegram, it is a more straightforward path with fewer account requirements and no business verification process. For Telegram options, see Claude Connectors for Telegram.

Recording follow-up work outside the thread

A WhatsApp conversation thread is not a reliable record of follow-up tasks. Threads scroll, notifications get cleared, and commitments made in a message get lost in the history. For customer service, sales, or project communication on WhatsApp, keeping the follow-up tasks in a separate record means nothing is dropped when the thread moves on.

How to do this with fenbs

1. Create a free account and add a project for the WhatsApp-related work.
2. For each follow-up commitment made in a WhatsApp thread, add a task to the fenbs board so it is tracked outside the conversation.
3. Record approved message templates and reply rules as Decisions and rules, so the AI works within the agreed framework.
4. Connect your AI via Integrations so it reads the rules and outstanding tasks at the start of each session.
5. For a team using WhatsApp for customer communication, give each team member a role in fenbs so the right people see the right tasks.

For Claude connector types in general, see Claude Connectors Explained. For the Telegram alternative for messaging workflows, see Claude Connectors for Telegram. More guides are in the connect-ai topic.