WhatsApp Business API by Wassenger

WhatsApp chat message analysis tool. Supports delivery-status lookups and chat export. The 'device' parameter accepts a device ID (24-hex), phone number (E.164), or alias — auto-selected if the account has a single device; otherwise the tool errors with the list of available devices so you can ask the user. Available actions: - delivery_status: Check delivery and read receipts for specific outbound messages (≤30 days old) - export: Export chat messages in JSON, CSV, or TXT format

Reports and exports of the chats of a WhatsApp number. Available actions: - statistics: the team's figures for a period (7 days by default, up to 92): new, resolved and reopened chats, messages received and sent, internal notes, average time to the first reply, to each reply, to resolve and to handle a chat, what was in the inbox at the end of the period, the most used labels and a day-by-day breakdown. Add compareFromDate and compareToDate to compare with an earlier period and get the change in percent. Days are cut at midnight in the account timezone, so for whole days pass local midnights with their offset. Times are in seconds. There is no breakdown per agent or per hour. - export: Export chats in JSON, CSV or TXT, filtered by status and date, paging through as many chats as requested Use this tool for: weekly reports, response time reviews, backups, and feeding chat lists into another system.

Create a WhatsApp message template and submit it to WhatsApp for review (WhatsApp Business API numbers only). It works in steps. Call it with whatever the user has given so far: if anything is missing or breaks a WhatsApp rule, it returns needsInput with the exact questions to ask, and nothing is created. When everything is valid it returns a preview and a confirmToken, still without creating anything. Show the preview; only after the user approves, call it again with the same fields plus the confirmToken. Supports text, image, video, document and location headers, body variables ({{1}} or {{first_name}}) with sample values, a footer, quick reply, URL, phone number and copy code buttons, and authentication (one-time code) templates.

Delete an uploaded WhatsApp file permanently. This action cannot be undone and will remove the file from storage. The file will no longer be available for sending in messages.

Delete one WhatsApp message template, in one language, from a WhatsApp Business API number. It works in two steps: called without a confirmToken it only reports which template would be deleted and returns a token, writing nothing; the deletion happens on a second call carrying that token, after the user approved it. It never deletes more than the template it reported, and it asks which language when the name exists in several.

Download the content of a received file from a WhatsApp chat. Returns the file content in the specified format: URL only (default) or base64 encoded content.

Download the content of an uploaded WhatsApp file. Returns the file content in the specified format: URL only (default) or base64 encoded content.

Export WhatsApp chats list in various formats for backup, analysis, or reporting purposes. Same as analyze_whatsapp_chats with action "export".

Retrieve archived WhatsApp chats. Useful for accessing historical conversations and managing chat organization. Same as get_whatsapp_chats with action "archived".

Retrieve WhatsApp chats assigned to specific agents or departments. Essential for agent workload management and performance tracking. Same as get_whatsapp_chats with action "assigned".

Retrieve detailed information about a specific chat using its WhatsApp ID. Includes complete metadata, assignment info, and activity details. Same as get_whatsapp_chats with action "by_id".

Get detailed information about a specific received file from a WhatsApp chat by ID. Returns complete file metadata including sender information, chat context, media details, and download URLs.

Retrieve WhatsApp chat messages (both inbound and outbound) for a specific device. Backed by the device-scoped Chat Messages endpoint, which requires a Platform subscription on the target device. Available actions: - recent: Latest messages in a chat (newest first by default) - search: Text search across messages (within a chat or device-wide) - date_range: Messages in a specific time window - by_sender: Messages sent from a specific phone number or WID - by_type: Messages filtered by type (text, image, video, audio, document, location, contact, etc.) - by_id: Fetch a specific message by its WhatsApp message ID - thread: Get conversation context around a specific message (N before + target + N after) - media: Messages containing media files The 'device' parameter accepts a device ID (24-hex), phone number in E.164 format, or device alias (e.g., "Sales 2") — pass exactly what the user named in their request. If the account has a single device, omit it and it will be auto-selected. If the account has multiple devices and the user didn't name one, the tool returns an error listing available devices — ask the user which one they mean.

Figures of the team for a period: chat and message volumes, response and resolution times, and what was in the inbox at the end of the period, optionally compared with an earlier period. Same as analyze_whatsapp_chats with action "statistics".

Comprehensive WhatsApp chat retrieval tool supporting all chat operations through a unified action-based interface. Perfect for accessing chat lists, searching conversations, filtering by various criteria, and managing chat data. Supports all WhatsApp chat retrieval operations with consistent formatting. Available actions: - recent: Most recent chats - unread: Chats with unread messages - by_status: Filter by chat status (pending, active, resolved, archived...) - assigned: Chats assigned to an agent or department, or to anyone - unassigned: Chats nobody is handling yet - by_contact_type: Filter by chat type (chat, group, community, channel) - by_id: One chat by its WhatsApp ID - search: Free text search over phone, name, contact, company, metadata and private notes - archived: Archived chats - by_date_range: Chats by last message, first message or last inbound message date Every action accepts labels, labelsExclude, status and contactTypes as extra filters. To find leads that went quiet, use by_date_range with activityType "lastInbound" and a toDate: those are the chats where the customer has not written since then.

Filter WhatsApp chats by contact type (individual users, groups, communities, channels). Useful for analyzing different communication patterns. Same as get_whatsapp_chats with action "by_contact_type".

Retrieve WhatsApp chats that were active within a specific date range. Perfect for analyzing conversation patterns and generating reports. Same as get_whatsapp_chats with action "by_date_range".

Search and filter WhatsApp chats by their platform status (active, pending, resolved, etc.). Useful for workflow management and chat organization. Same as get_whatsapp_chats with action "by_status".

Retrieve comprehensive detailed information about a specific WhatsApp device using its ID. Returns complete device configuration, session status, metrics, and actionable insights. For WhatsApp Cloud API numbers it includes the health Meta reports: quality rating, messaging limit, payment problems, restrictions and the issues Meta lists with their fix. Use it to find out why messages are not going out.

Comprehensive tool to retrieve WhatsApp devices with flexible filtering options. Supports all device query scenarios: get all devices, filter by status/session status, search by terms, get only active/online devices, etc.

Get detailed information about a specific uploaded WhatsApp file by ID. Returns complete file metadata including size, type, format, status, expiration, tags, and download URLs.

Retrieve WhatsApp chats with unread messages. Essential for managing pending conversations and customer support. Same as get_whatsapp_chats with action "unread".

Comprehensive health check of the MCP server and connected WhatsApp devices.

List what customers answered in a WhatsApp Form (Meta WhatsApp Flow), newest first: who answered, each question's label and value, and when. Takes the form's id from list_whatsapp_flows (not its flowId). Only keys of the account owner or an admin can read answers.

List WhatsApp Flows available for a device (WABA). Returns flow id, name, status, categories and entry screen. Use this to find a flow to send.

Retrieve WhatsApp templates for a specific device (approved ones by default). Each template includes its components and the variables that must be filled in to send it. This is required for sending template-based messages.

Universal WhatsApp campaign contacts management tool that handles all campaign recipient operations through action-based parameters. Supports add, remove, and search operations for campaign recipients: phone numbers and groups. Essential for WhatsApp campaign recipient management. add keeps the recipients already on the campaign. On a campaign that sends a template (WhatsApp Cloud API numbers), give every variable its component exactly as on manage_whatsapp_campaigns create: body, header, header_location, button_url_N or button_copy_code_N, with N the buttonIndex that list_whatsapp_templates reports. Such a campaign only reaches phone numbers, not groups. On a campaign from a number linked by QR, each variable key fills the {{ key }} placeholder of the campaign message.

Universal WhatsApp campaign management tool that handles all campaign operations through action-based parameters. Supports search, create, update, start, stop, and delete operations for WhatsApp bulk messaging campaigns. Perfect for comprehensive WhatsApp marketing automation. What a campaign sends depends on the number. Its connector, reported by get_whatsapp_devices and health_check, says which kind it is: cloud for WhatsApp Cloud API, web for a number linked by QR. - WhatsApp Cloud API (WABA) numbers: a pre-approved template is required, and it only reaches phone numbers, never groups. Pass template { name, language } and give each recipient the values its variables need. Read the template first with list_whatsapp_templates: every variable it reports has a location (header, body or buttons) and, for buttons, a buttonIndex starting at 0. Send each value with its component, and for a button variable use button_url_N or button_copy_code_N with that index. - Numbers linked by QR: a message, optionally with a file. Personalize it with placeholders: {{ name }} is the recipient's name, {{ phone }} their number, and each key in a recipient's variables fills {{ key }}. For example message "Hi {{ name }}, your order {{ order }} has shipped" with variables [{ key: "order", value: "A-1043" }]. Write keys and placeholders in lowercase. A placeholder a recipient has no value for disappears from their message; {{ order | on its way }} prints the text after the bar instead. To send it: create with activate true, which needs settings.date and at least one recipient, or create first and then start, which asks for the same two. If activation fails during create, the campaign is deleted and you have to create it again. Recipients: pass them on create, up to 2000 per request. To add or remove them afterwards use manage_whatsapp_campaign_contacts. The total a campaign can hold depends on the plan, from 100 on trial to 2000. What it will cost: before launching a template campaign,…

Comprehensive WhatsApp channel message management tool for retrieving and managing channel content. Perfect for monitoring channel activity and accessing channel message history. Available actions: - get: Get recent messages from a specific channel with filtering options

Comprehensive WhatsApp channel management tool supporting all channel operations. Perfect for managing channel lifecycle, membership, and content. Supports all WhatsApp channel operations through a unified action-based interface. Available actions: - list: List and retrieve channels with filtering options - get: Get detailed information about a specific channel - create: Create new channels with optional profile images - update: Update existing channel information (name, description) - search: Search for public channels by category and keywords - join: Join/follow channels via invite code or URL - leave: Leave/unfollow channels - delete: Delete channels (alias for leave) - update_image: Update channel profile images

Change a WhatsApp chat in the team inbox without sending anything to the customer: hand it to a teammate or department, add or remove labels, resolve or reopen it, leave an internal note, or mark it read or unread. The customer sees none of it. Your team sees the change, and your account's chat webhooks are notified. Available actions: - assign: give the chat to agentId, agentEmail or departmentId (departments need a plan that includes them). A pending chat becomes active. - unassign: take the chat off its agent and department. It goes back to pending. - add_labels / remove_labels: the labels must already exist on the number, create them first with manage_whatsapp_labels. The chat keeps any label you do not mention. - resolve: close the conversation. - reopen: back to active if someone owns the chat, pending otherwise. - add_note: private note only your team can see (2 to 6000 characters). authorId writes it as that teammate. - mark_read / mark_unread: marking a resolved chat as unread reopens it. To write to the customer, use send_whatsapp_message instead.

Manage WhatsApp contact blocking and unblocking operations. Handle contact blocking status with action-based operations to control message reception from specific contacts. Contacts are identified by phone number in E.164 format, not by WhatsApp ID.

Comprehensive WhatsApp contacts management with action-based operations. Supports listing, searching, creating, updating, deleting contacts, bulk operations, and metadata management. All contact operations including CRUD, filtering, pagination, and metadata handling in one unified tool.

Comprehensive WhatsApp deal note management tool supporting all note operations. A note is what somebody wrote on a sales deal; a note that carries a due date IS a task. Perfect for managing sales notes, tracking tasks, and attaching files to deals. Supports both standalone notes and comments nested under deal history events. Available actions: - list: Retrieve all notes for a deal with filtering and metadata - create: Create a new note (optionally as a task with due date, or as a comment on a deal event) - update: Update note text, due date, completion status, or file attachments - delete: Remove a note (requires confirmation) Note: The Sales Funnel API is available on the Platform Professional subscription and above. Write endpoints return HTTP 403 when the account's plan does not include it; read endpoints are deliberately NOT plan-gated. Restricted agents (plain agent role) only ever receive their own deals, regardless of filters.

Comprehensive WhatsApp sales funnel deal management tool. A deal is one sales opportunity tied to a WhatsApp contact, sitting in one stage of one pipeline. Supports listing, retrieving, creating, updating, archiving, moving between stages, linking to chats, and fetching event history. Available actions: - list: Retrieve deals with rich filtering (pipeline, stage, status, agent, contact, device, stalled, chatStatus, unread, updatedAfter/Before, pagination) - get: Retrieve a single deal by ID - create: Create a new deal (requires pipeline, device, contactWid) - update: Update deal fields (title, amount, currency, agent, department) - stage moves are NOT here, use move_stage - archive: Archive a deal (frees the contact's open-deal slot, preserves as sales history) - move_stage: Move a deal to another stage (requires previousStage for atomic compare-and-swap) - link_chat: Link a deal to a WhatsApp conversation by contactWid - events: Fetch deal event history (limit, skip) Important notes: 1. move_stage requires previousStage - the stage the client last saw. The server performs an atomic compare-and-swap and answers 409 when it no longer matches. Always read the deal first (action: 'get') and pass its current stage value. 2. Only ONE open deal may exist per contact per pipeline. The API answers 409 otherwise, and the check spans the @c.us/@lid identity equivalence. 3. Restricted agents (plain agent role) only ever see their own deals, regardless of filters. 4. Write operations (create, update, archive, move_stage, link_chat) require the Professional plan or above. Read operations (list, get, events) are not plan-gated.

Comprehensive WhatsApp department management tool supporting all department operations. Perfect for organizing team structure, managing agent assignments, and customizing department appearance. Supports all WhatsApp department operations through a unified action-based interface. Available actions: - list: List and retrieve all departments with complete information - create: Create new departments with agents, colors, and icons - update: Update existing department information and agent assignments - delete: Delete departments (removes department but preserves agent assignments)

Universal WhatsApp group participants management tool that handles all participant operations through action-based parameters. Supports add, remove, promote, demote, and approval management operations. Essential for WhatsApp group moderation.

Universal WhatsApp group management tool that handles all group operations through action-based parameters. Supports search, create, update, join, leave, and invite management operations. Perfect for comprehensive WhatsApp group administration.

Comprehensive WhatsApp label management tool supporting all label operations. Perfect for organizing conversations with color-coded categories and managing chat organization systems. Supports both WhatsApp Business and platform-specific labels. Available actions: - list: Retrieve all available labels with filtering and metadata - create: Create new labels with custom colors and descriptions - update: Update existing label colors and descriptions - delete: Remove labels and cleanup associated chats