Teams that live in Slack and serve clients on WhatsApp end up with one person glued to the phone. When people search how to integrate WhatsApp with Slack, what they usually need is not a copy of every message in a channel, but the team knowing who is waiting and what they asked.
Checked on November 16, 2026.
Two routes
Route 1, an AI agent with two MCP servers. WACrew's MCP reads your WhatsApp; Slack's official MCP server (Slack docs), hosted by Slack, lets the same agent search and post in your workspace. Slack controls access through apps and OAuth, so a workspace admin may need to approve it.
Route 2, no AI: n8n on the WACrew API. The WACrew panel has an API v1 with a /radar endpoint that lists who is without an answer. An n8n workflow can call it every few minutes with a read token and post to a channel with n8n's Slack node.
Route 1, step by step
- Run the WACrew panel and connect your number (README).
- Add both servers to your agent (Claude Code shown):
claude mcp add wacrew -e WAC_CLOUD_URL=https://your-panel.example.com \
-e WAC_CLOUD_USER=admin -e WAC_CLOUD_PASS=change-me -- npx -y wacrew-mcp
claude mcp add --transport http slack <URL from the Slack MCP docs>
- Ask:
Who is waiting for a reply on WhatsApp? Post the list in #clients, one line per
client: name, how long they have waited and what they asked. No message contents
beyond that.
Route 2, step by step
- On the server:
node scripts/api-token.mjs criar n8n-slack --escopos read. - In n8n: Schedule trigger, then HTTP Request to
https://your-panel.example.com/api/v1/radarwith headerAuthorization: Bearer <token>, then the Slack node posting a short list. - Post only when the list changes, so the channel does not become noise.
Limits
- Route 1 runs while an agent session is open; Route 2 runs on n8n's schedule, not instantly.
- Think about what goes into Slack: client messages may contain personal data. A list of names and wait times is usually enough.
- Replies still go out from WhatsApp. Team members can answer from the WACrew panel with their own login, limited to the chats you release to them.
Questions
Can my team reply to WhatsApp from Slack? Not with these routes. They see the alert in Slack and reply in the WACrew panel, where each login only sees the chats you allow and every message records who sent it.
Does this need the WhatsApp Business API? No. WACrew links to your existing number as a device.
Can the agent post a daily summary? Yes. Ask it to read the chats that moved today and post one summary per client in a channel or thread.
Is there a Slack app for WACrew? No. The bridge is the agent or n8n.



