Summary
Wazzup (wazzup24.com), a paid gateway that connects WhatsApp, WhatsApp Business API, Telegram, Instagram, MAX, VK, Viber and Avito to a CRM: list channels, send messages and WABA templates, sync CRM users, contacts, deals and pipelines, read the unanswered counter, open the chat window and manage webhooks. API key.
Guided setup
Connect Wazzup to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Wazzup in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Wazzup
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Wazzup, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Wazzup + Microsoft Copilot
Wazzup (wazzup24.com), a paid gateway that connects WhatsApp, WhatsApp Business API, Telegram, Instagram, MAX, VK, Viber and Avito to a CRM: list channels, send messages and WABA templates, sync CRM users, contacts, deals and pipelines, read the unanswered counter, open the chat window and manage webhooks. API key.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
WAZZUP_API_KEY
Step 1 — Get credentials
Setting up takes about 3 minutes.
- Sign in to your Wazzup account and add at least one channel under Channels (a paid subscription is needed for a channel to work).
- Open Integration with CRM, choose API and click Connect. Wazzup has one CRM integration per account: an account already connected to amoCRM, Bitrix24, HubSpot or Zoho has a sidecar API key instead, shown in the settings of that integration.
- Copy the API key into
WAZZUP_API_KEY. Later it is under Integration with CRM, tab Advanced.
Where to start: wazzup_list_channels gives the channelId and transport of every connected messenger account and its state. Then wazzup_send_message with that channelId, a chat_type that matches the transport, and the recipient.
Sending: wazzup_send_message sends text or one file by link (never both in one call), a WABA template (template_id from wazzup_list_whatsapp_templates) or a message with buttons. For WhatsApp and Viber chat_id is the phone in digits only (79011112233). For Telegram and MAX use phone or username when the chat id is not known; the answer returns the chatId to use next time. The call is not idempotent: pass crm_message_id to block a repeat within 60 seconds. wazzup_edit_message changes the text or the file of a sent message where the messenger allows it; wazzup_delete_message is installed switched off.
Delivery statuses and incoming messages are not readable on request: Wazzup posts them to a webhook address. wazzup_get_webhooks shows the address and subscriptions; wazzup_set_webhooks (switched off) replaces them, and Wazzup first sends a test POST that the address must answer with 200.
CRM sync: Wazzup shows a chat to the user who is responsible for the contact or the deal, so these lists must match the CRM. wazzup_list_users, wazzup_get_user, wazzup_upsert_users; wazzup_list_contacts, wazzup_get_contact, wazzup_upsert_contacts; wazzup_list_deals, wazzup_get_deal, wazzup_upsert_deals; wazzup_list_pipelines, wazzup_upsert_pipelines. Upserts match by id (your CRM's id), take at most 100 entries per call and update what exists. wazzup_delete_user, wazzup_delete_contact and wazzup_delete_deal are installed switched off; the bulk delete routes are not included.
Unanswered and chat window: wazzup_get_unanswered_count returns the unanswered chats of one CRM user over the last 7 days. wazzup_create_chat_window_link returns a link that opens Wazzup's chat window as that user: treat it like a sign-in link and give it only to that person.
Limits and errors: 500 requests per 5 seconds. Errors come as JSON with error (a code such as INVALID_APIKEY, WRONG_TRANSPORT, INVALID_MESSAGE_DATA, TOO_MANY_ENTITIES) and description. A sidecar key only works for the channel list, sending, webhooks and the template list; other routes answer 403. Sending a WABA template is charged by Meta through the WABA balance of the account (BALANCE_IS_EMPTY when it is used up).
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Wazzuptools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
wazzup_list_channels | List the messenger accounts (channels) connected to the Wazzup account: channelId (uuid), transport (whatsapp, wapi for WhatsApp Business… |
wazzup_send_message | Send a message through one channel: text, or one file by link, or a WhatsApp Business API template, optionally with buttons. Returns… |
wazzup_edit_message | Change the text or the attached file of a message already sent through Wazzup (one of the two, not both). Works where the messenger allows… |
wazzup_delete_message | Delete a sent message for both sides in the messenger, where the channel supports it (Telegram Bot, MAX Bot). The Wazzup chat window keeps… |
wazzup_list_whatsapp_templates | List the WhatsApp Business API (WABA) message templates of the account: templateGuid (the code for template_id when sending), title, name… |
wazzup_list_users | List the CRM users (employees) known to Wazzup, sorted by name: id (the CRM's user id) and name. These ids are used as responsible user for… |
wazzup_get_user | Read one CRM user known to Wazzup: id, name and phone (international format, used to invite the user to the mobile app). Read-only |
wazzup_upsert_users | Add or update CRM users in Wazzup, matched by id: a new id is added, an existing one is updated. At most 100 users per call and 1000 users… |
wazzup_delete_user | Remove one CRM user from Wazzup. The user loses access to the chats in Wazzup. Installed switched off |
wazzup_list_contacts | List the contacts synced to Wazzup, sorted by id ascending: count (total) and data with id (the CRM's contact id), responsibleUserId, name… |
wazzup_get_contact | Read one contact synced to Wazzup: id, responsibleUserId, name, contactData (chatType, chatId, username, phone) and uri. Read-only |
wazzup_upsert_contacts | Add or update contacts in Wazzup, matched by id. The responsible user decides who sees the chat with this contact in Wazzup. At most 100… |
wazzup_delete_contact | Remove one contact from Wazzup's copy of the CRM. A chat with this contact stays in the general chat list. Answers 404 when the contact… |
wazzup_list_deals | List the deals synced to Wazzup: count and data with id (the CRM's deal id), responsibleUserId, name, contacts (ids of the linked contacts)… |
wazzup_get_deal | Read one deal synced to Wazzup: id, responsibleUserId, name, uri, contacts (ids of the linked contacts) and closed. Read-only |
wazzup_upsert_deals | Add or update deals in Wazzup, matched by id. A deal links contacts to a responsible user, who then sees their chats, and appears in the… |
wazzup_delete_deal | Remove one deal from Wazzup's copy of the CRM. Answers 404 when the deal does not exist. Installed switched off |
wazzup_list_pipelines | List the sales pipelines uploaded to Wazzup with their stages (id and name each). Wazzup uses them to choose where a deal for a new… |
wazzup_upsert_pipelines | Upload or update the CRM's sales pipelines and their stages in Wazzup, so that the account settings can pick the pipeline and stage for… |
wazzup_get_unanswered_count | Read how many chats wait for an answer from one CRM user over the last 7 days: counterV2 (number), type (red for chats the user is… |
wazzup_create_chat_window_link | Create a link that opens Wazzup's chat window (iframe) as one CRM user: all chats of that user (scope global) or only the chats listed in… |
wazzup_get_webhooks | Read the webhook settings of the integration: webhooksUri (the address Wazzup posts to) and subscriptions (messagesAndStatuses… |
wazzup_set_webhooks | Set the address Wazzup posts events to and which events it sends. It replaces the current address, so an existing integration stops… |
Example prompts
- "Which messenger channels are connected to Wazzup, and are they all active?"
- "Send a WhatsApp message to 79011112233 on our sales channel: your order is ready for pickup."
- "How many chats has manager Olga left unanswered in the last 7 days?"
- "Which WABA templates can I send?"
- "Add the deal Office furniture, 450,000 rubles, for contact Ivan Smirnov, responsible Olga."
FAQ
Where does the API key come from? In your Wazzup account add at least one channel, open Integration with CRM, choose API and click Connect; the key is later under the Advanced tab. If the account is already connected to amoCRM, Bitrix24, HubSpot or Zoho, use the sidecar API key of that integration, which only works for the channel list, sending, webhooks and templates.
What is Wazzup, and what does the connector cover? Wazzup is a paid gateway (a subscription per channel) that connects WhatsApp, WhatsApp Business API, Telegram, Instagram, MAX, VK, Viber and Avito to a CRM. The connector lists channels, sends and edits messages, sends WABA templates (Meta charges them to the account's WABA balance), syncs CRM users, contacts, deals and pipelines, reads the unanswered counter and opens the chat window. Delivery statuses and incoming messages are not readable on request: Wazzup posts them to a webhook.
Which tools install switched off? wazzup_delete_message, wazzup_delete_user, wazzup_delete_contact, wazzup_delete_deal and wazzup_set_webhooks. Switch them on on the connector page only if the AI should use them.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?