Slack WhatsApp Integration: How to Connect WhatsApp Business to Slack
Neither Meta nor Slack publishes a native WhatsApp app for Slack. Four routes fill the gap, and they are not equally safe. Two run on Meta's official Cloud API. Two drive a logged in phone through WhatsApp Web, which is the route that gets numbers banned.
WaBulkSend runs on Meta's official WhatsApp Cloud API. Not affiliated with Slack Technologies or Meta Platforms, Inc.
Which route fits your setup?
No sign inThe free WhatsApp Business app has no API. Every tool that puts an app number into Slack does it by driving a logged in session through WhatsApp Web, which is the automated behavior WhatsApp's terms prohibit. Register the number on the Cloud API first, then pick an official route.
One-way notifications are the easy case. A workflow tool subscribes to the Cloud API messages webhook and posts each message to a Slack channel. No custom server to maintain.
Two-way needs a piece of software that keeps thread state, maps each Slack thread back to a customer, and enforces the 24 hour window. Buy a bridge app or build a small Slack app against the Cloud API.
Slack is a bad campaign surface. It has no contact list, no template manager, and no delivery reporting. Send the campaign from a WhatsApp platform and use Slack for the replies that come back.
Meta bills you per delivered template on your own WhatsApp Business account whichever route you pick. Slack adds no WhatsApp charges of its own.
Short answer: there is no official WhatsApp integration for Slack. Meta does not publish a Slack app, and Slack does not ship a WhatsApp connector, so every working setup uses a third party in the middle. You have four practical routes: a workflow tool such as Zapier, Make, or n8n for one-way notifications; a ready made bridge app that installs into your workspace for two-way conversations; a custom Slack app you build against Meta's Cloud API; or a QR code bridge that logs into a normal WhatsApp number through WhatsApp Web. The first three run on Meta's official Cloud API and stay inside WhatsApp's terms. The fourth automates a consumer account, which WhatsApp's terms prohibit, and it is the reason numbers get banned. Whichever you choose, Slack itself never becomes the sender: it is a viewing and reply surface on top of a WhatsApp Business account you still own and pay Meta for.
Last updated August 2026. Slack is a trademark of Slack Technologies, LLC. WhatsApp is a trademark of Meta Platforms, Inc. WaBulkSend is not affiliated with either.
Does Slack have a WhatsApp integration?
No. Slack's app directory has no WhatsApp app published by Meta, and Meta's own list of WhatsApp integrations does not include Slack. This is not an oversight. The WhatsApp Business Platform is an API rather than a consumer chat network you can plug a workspace into, and access to it runs through Meta's Cloud API or an approved solution provider. So the question people are really asking is not whether Slack supports WhatsApp, but which third party to put between them.
That choice matters more than it looks, because the middle layer decides whether you are automating an official business account or a personal one. Here are the four routes that actually work in 2026, side by side.
| Route | How it connects | Two-way replies | Policy status |
|---|---|---|---|
| Workflow tool Zapier, Make, n8n |
Official WhatsApp Cloud API connector on one side, official Slack connector on the other. n8n ships a WhatsApp Business Cloud node plus a WhatsApp Trigger, and a Slack node. | Possible but clumsy. There is no thread state, so replies from Slack need a slash command or form step you build yourself. | Official Cloud API. Inside WhatsApp terms. |
| Bridge app installs into the workspace |
A vendor runs a shared inbox on your WhatsApp Business account and mirrors it into Slack channels or threads. Social Intents, for example, documents that its Slack integration uses Meta's official WhatsApp Business API and requires a verified WhatsApp Business Account. | Yes, this is the point of it. Each customer maps to a channel or a thread and agents answer without leaving Slack. | Official Cloud API when the vendor is a real solution provider. Verify before you buy. |
| Custom Slack app you build it |
Your server subscribes to the Cloud API messages webhook, posts to Slack with the Web API, and sends replies back to graph.facebook.com from a Slack event handler. | Yes, and you control the thread model, routing, and audit trail completely. | Official Cloud API. Inside WhatsApp terms. |
| QR code bridge no API needed |
You scan a QR code with a normal WhatsApp or WhatsApp Business app number and the vendor holds that logged in session open, relaying messages to Slack. 2Chat, for instance, markets connecting a regular WhatsApp number by scanning a QR code with no WhatsApp Business API required. | Yes, and setup takes minutes, which is exactly why it is tempting. | Unofficial automation. WhatsApp's terms prohibit it and the number can be banned. |
Vendor names are examples of each pattern, drawn from the vendors' own public documentation, not endorsements. If you are choosing between workflow tools specifically, the n8n WhatsApp integration, the Make WhatsApp integration, and the Zapier WhatsApp integration each behave differently on triggers and cost.
The QR code shortcut is the one that gets numbers banned
The free WhatsApp Business app has no API. None. So when a tool promises to put your existing WhatsApp number into Slack in five minutes with a QR scan, it is not integrating with anything Meta built. It is running an automated client against a consumer session, the same way a browser extension would. WhatsApp's terms of service prohibit bulk messaging, auto-messaging, auto-dialing, and the like, and enforcement lands on the phone number, not on the vendor.
This is a real cost, not a theoretical one. A banned number takes your message history and your customers' saved contact with it, and a phone number can be registered to only one WhatsApp account at a time, so you cannot simply move it somewhere clean. Businesses that lose a main line this way usually discover the number was also printed on packaging, invoices, and a Google Business Profile.
How to tell which kind of tool you are looking at
Read the setup step. If onboarding asks you to scan a QR code with your phone, it is a WhatsApp Web bridge. If it asks for a Meta Business Manager login, a WhatsApp Business Account ID, and a phone number you register and verify with Meta, it is the Cloud API. There is no third possibility, and no amount of dashboard polish changes which one you are on.
The official path costs more effort up front. You register a number on the WhatsApp Business Platform, complete Business Verification, and accept per-message billing by category and country. In exchange the account is yours, it survives, and it scales past the 256 recipient cap that a broadcast list imposes. Our page on WhatsApp bulk messaging rules covers what is allowed once you are on the official platform.
How to connect WhatsApp to Slack in five steps
This is the official Cloud API path, the one that works for notifications and can be extended to two-way replies.
Put the number on the WhatsApp Business Platform and collect the access token, WhatsApp Business Account ID, and phone number ID from Meta.
Subscribe to the messages field. Your endpoint must use HTTPS with a valid certificate, since self-signed certificates are not supported, and return HTTP 200.
In your Slack workspace, add an app with an incoming webhook or the chat.postMessage scope, and pick the channel that will hold customer messages.
Meta nests the message under entry then changes then value, and both of those are arrays. Pull the sender, the text, and the timestamp, then post one Slack message per customer thread.
Handle the Slack message event, check the customer wrote to you in the last 24 hours, and post to the Cloud API. Outside that window you must send an approved template instead.
Step five is where most builds get stuck, and it is a policy limit rather than a coding problem. Meta signs every webhook with an X-Hub-Signature-256 header, an HMAC SHA256 of the raw request body, so verify that before you trust a payload. The full setup is documented on our WhatsApp Cloud API page.
What works once WhatsApp is in Slack, and what does not
Putting WhatsApp in Slack solves visibility. It does not remove any of Meta's messaging rules, and teams are regularly surprised by which ones follow them into the workspace.
| What you want to do from Slack | Does it work? | Why |
|---|---|---|
| See every incoming WhatsApp message in a channel | Yes | The messages webhook fires on every inbound message. This is the simplest and most reliable half of the integration. |
| Reply in free text to a customer who just wrote in | Yes, for 24 hours | The customer service window opens when they message you and closes 24 hours after their last message. Inside it you can send any message type. |
| Message someone who has not written to you recently | Template only | Outside the 24 hour window only an approved template can open a conversation. A plain Slack message will be rejected by the API. |
| Send marketing templates to US phone numbers | No | Meta paused delivery of marketing category templates to US numbers on April 1, 2025 and returns error 131049. Utility and authentication templates still deliver. |
| Blast one template to your whole contact list | Not from Slack | Slack has no contact list, no template manager, and no delivery reporting. Campaigns belong in a sending platform; Slack handles the replies. |
| Send as fast as your team can type | Within limits | The Cloud API handles up to 80 messages per second by default, but a per-user brake allows only one message every six seconds to the same person. |
A cost change lands on October 1, 2026, and it hits this exact use case
Replying to customers inside the 24 hour window is the whole reason to put WhatsApp in Slack, and those replies are free today. Meta made service conversations free for all businesses on November 1, 2024. Multiple solution providers, including Wati, SendPulse, and charles, now say Meta will reintroduce per-message charges for service messages on October 1, 2026, priced at the same per-country rate as utility templates and with no volume discounts.
Treat that as a strong signal rather than settled fact for now. Meta's public pricing page still states that service conversations are free and has not published the new rate card. Under Meta's own governance rule, pricing changes take effect only on the first day of a quarter with one month of advance notice, so the final per-country rates are due by September 1, 2026. If you are budgeting a Slack based support desk for Q4, model the replies at your country's utility rate rather than at zero. We track this on the WhatsApp pricing changes page.
Who each route is actually for
The right answer depends on how many people need to touch the conversation.
Nobody wants to miss a customer message overnight. One Zapier or Make scenario posting inbound messages to a channel solves it in an afternoon, and replies still happen in the WhatsApp inbox.
If tickets, alerts, and escalations already live in Slack, a bridge app that maps each customer to a thread keeps agents in one window. Check the vendor is on the official API before you commit a main line to it.
If you need conversations routed by product line, region, or account tier, build the Slack app yourself. You get the thread model you want and no per-seat fee on top of Meta's message charges.
Slack is the wrong tool for outbound. Send approved templates from a platform built for it, then pipe the replies into Slack so the team can pick them up. That split is what most mature setups land on.
If more than a couple of people need to answer the same number, the underlying problem is shared access rather than Slack specifically. Our guides on the WhatsApp shared inbox and on WhatsApp Business with multiple users cover how many agents one number can realistically support.
Frequently asked questions
Does Slack have WhatsApp integration?
Not officially. Slack's app directory contains no WhatsApp app published by Meta, and Slack ships no WhatsApp connector of its own. Every working integration puts a third party in between: a workflow tool such as Zapier, Make, or n8n, a bridge app you install into the workspace, or a custom Slack app built against Meta's WhatsApp Cloud API.
Can I connect WhatsApp to Slack?
Yes, and it is a common setup. The reliable version registers your number on Meta's WhatsApp Cloud API, subscribes to the messages webhook, and posts each inbound message into a Slack channel. Replies go back through the Cloud API. Setup takes a few hours with a workflow tool, or a day or two for a custom Slack app with proper thread mapping.
Can you reply to WhatsApp messages from Slack?
Yes, with one rule attached. You can send free-form replies only within 24 hours of the customer's last message. That window opens when they message you and refreshes each time they write again. After it closes you can only reach that person with a template Meta has already approved, which means a Slack reply typed at hour 30 will be rejected by the API.
Will connecting WhatsApp to Slack get my number banned?
It depends entirely on the route. Anything built on Meta's official Cloud API is a supported use and carries no ban risk from the integration itself. Tools that ask you to scan a QR code are automating a consumer WhatsApp session, which WhatsApp's terms prohibit, and enforcement falls on your phone number rather than on the vendor.
How much does a WhatsApp Slack integration cost?
Three costs stack up. Slack charges its normal per-seat price and adds nothing for WhatsApp. The middle layer costs whatever the workflow tool or bridge app charges, or nothing if you build it. Meta bills you separately per delivered template by category and country, on your own WhatsApp Business account, no matter which route you use.
Can Slack send bulk WhatsApp messages?
No, and it is worth being clear about why. Slack has no contact list, no template manager, no send scheduling, and no delivery reporting, so a broadcast would mean looping an automation over a spreadsheet with no visibility into who received anything. Send campaigns from a platform built for it and use Slack for the conversations that come back.
Do I need the WhatsApp Business API to connect Slack?
For any route worth running, yes. The free WhatsApp Business app has no API at all, so tools that work with it drive a logged in session through WhatsApp Web. Registering on the Cloud API requires a number you own that can receive a call or SMS and is not already registered to another WhatsApp account.
Can I connect WhatsApp to Microsoft Teams instead?
The situation is identical. Microsoft publishes no native WhatsApp connector for Teams, so you use the same three official patterns: a workflow tool, a bridge app on the Cloud API, or a custom app against the messages webhook. The 24 hour window, template approval, and per-message billing all apply exactly the same way.
Keep Slack for conversations, send campaigns properly
Slack is a good place to answer customers and a poor place to run a send. WaBulkSend is pre-launch and building campaign sending on Meta's official Cloud API. The plan is that the outbound side will handle approved templates, scheduling, and delivery reporting, while your team keeps replying wherever it already works.
Join the waitlist