WhatsApp Slack Integration: 6 Options, Prices and Limits

A WhatsApp Slack integration always needs a third-party tool: Slack has no native WhatsApp integration, and Meta does not publish an official Slack app. Your options are automation platforms (Zapier, Make), apps that connect your number to Slack, or your own code on top of an API.

The choice matters most for teams that work inside groups. Some options only push WhatsApp messages into Slack and stop there. Others let the team reply from Slack but cannot read groups. Few do both.

This guide compares six routes by what matters to a team day to day: whether replies go back to WhatsApp, whether groups work, what it costs and what can go wrong. Prices were checked on each vendor's official page on October 20, 2026.

Does Slack have an official WhatsApp integration?

No. As of October 2026, Slack offers no native WhatsApp integration, and we found no app in the Slack Marketplace published by Meta or by Slack itself. What exists are third-party apps that connect a WhatsApp number to Slack channels on their own terms.

So every WhatsApp Slack integration runs through a third company, and each one makes different choices on three points:

• How it connects to WhatsApp: through Meta's official API (WhatsApp Business Platform) or through the number you already use, linked by QR code.
• Where messages land: one channel per contact, one shared channel with a thread per conversation, or just a notification.
• Whether replies go back: two-way sync, or WhatsApp to Slack only.

On Slack's free plan, add one more limit: free workspaces can install at most 10 third-party apps and only show the last 90 days of messages (Slack, Usage limits for free workspaces). Older support history drops out of search.

Can the official WhatsApp API read groups?

It can, but it does not fit communities. The WhatsApp Cloud API groups feature exists, but it requires the business to be an Official Business Account (verified badge), caps groups at 8 participants and only lets people join through an invite link (Meta for Developers, Groups).

In practice, that rules out the most common reason people want WhatsApp groups in Slack: course cohorts, paid communities, B2B client groups with several people on each side. An 8-person group is a project group, not a community.

The official API also has conversation rules that affect any integration:

• Meta has charged per message since July 1, 2025; messages from users to the business are not charged (Meta for Developers, Pricing).
• Free-form replies only work inside the 24-hour window after the customer's last message. Outside it, only approved templates.

That is why tools that bring large groups into Slack almost always connect the number by QR code, outside the official API. That route has a different cost: the risk of the number being banned, covered below.

What are the options for a WhatsApp Slack integration?

There are six routes, from simplest to most work. The table sums up what each one does as of October 2026; details and sources follow.

Prices in USD from each vendor's official pages, checked October 20, 2026. They exclude Meta's per-message charges when the option uses the official API.

1. Zapier: quick for alerts, weak for support

Zapier links the WhatsApp Business app to Slack with a "New Message Received" trigger that fires "when a customer sends a message to your WhatsApp Business phone number" (Zapier, Slack + WhatsApp Business). The page does not mention groups.

• Good for: alerting the team in a channel when a new message arrives.
• Limit: each Zap runs one way. To reply from Slack you build a second Zap (a Slack message triggers a WhatsApp send), map the recipient and respect the 24-hour window. There is no ready-made thread per conversation.
• Cost: the free plan has 100 tasks a month and two-step Zaps only; Professional starts at $19.99/mo billed annually ($29.99 monthly) with 750 tasks (Zapier, Pricing). Every message uses a task.

2. Make: more flexible, same one-way logic

Make works like Zapier, with visual scenarios and more control over logic. The free plan gives 1,000 credits a month (Make, Pricing). The limit is the same: inbound and outbound are two separate scenarios, and conversation sync (who replied, to which contact) is up to you.

3. TimelinesAI: the Slack connection goes through Zapier

TimelinesAI connects WhatsApp numbers to CRMs and includes "native" Zapier and Make integrations on every plan. The vendor's own Slack guide, updated December 2025, builds the connection via Zapier, with triggers like "New Incoming Chats" sending notifications to a channel. The guide does not describe replying from Slack or groups.

On the pricing page (Oct 2026), Starter costs $35 per seat per month ($28 annual) and Pro $49 ($39 annual). "Groups API" appears as "coming soon" on the Enterprise plan.

4. Periskope: strong on groups, no native Slack

Periskope focuses on WhatsApp groups and lists integrations with HubSpot, Google Sheets, Freshdesk, Zoho Desk and Zapier, plus API and webhooks. Slack does not appear on its pricing page as a native integration (Oct 2026); the route is Zapier or the API. Starter costs $25 per user per month and Pro $35, with extra phones billed separately.

5. 2Chat: the closest to what a group team needs

2Chat connects the number by QR code and sends conversations to a Slack channel you choose. Each new conversation opens a thread, and a reply posted in the thread goes back to WhatsApp. The integration page says groups can be synced with Slack channels. The Basic plan, with Slack included, costs $49/mo ($40 annual); the Single plan does not include Slack (Oct 2026).

The catch is the single-channel, thread-based model: with many conversations a day, the channel becomes a long queue, and organization (who picked it up, what is resolved) depends on reactions and team habits.

6. Your own code: full control, your maintenance

You can build the bridge with a third-party WhatsApp API, a Slack app with the chat:write scope and a server that receives webhooks from both sides. A tutorial published by an API vendor shows the design: a group message becomes a Slack message, and the thread reply goes back to the group.

The same tutorial lists the traps: Slack expects your server to respond in under 3 seconds and retries the event on failure, which creates duplicate messages if you do not handle it. It makes sense if you have a developer and want control; for a support team, it is one more system to keep running.

What should you check before choosing a WhatsApp Slack integration?

Check four things, in this order: whether replies go back, whether groups work, how conversations are organized in Slack and what happens if the number goes down. Price comes after, because a cheap integration that only notifies still forces the team to reply from the phone.

1. Two-way sync. If replies do not go back from Slack, you built an alert feed, not a support channel.
2. Real groups. Test with your largest group: does it show the name of each sender, or only a number?
3. Organization. One channel per contact stays tidy but multiplies channels. One channel with threads stays central but turns into a queue. Decide what your team can handle.
4. Number risk. QR-code tools use your regular number. They carry no Meta per-message fee, but the number can be banned if usage looks like spam. Ask what happens to your groups if that happens.
5. Per-seat cost. Per-user pricing grows fast once the whole Slack workspace can see WhatsApp.

If your main problem is organizing groups, not just bringing them into Slack, read how to manage WhatsApp groups for business first.

When is Slack the right place to handle WhatsApp?

Slack is the right place when the people who need to see WhatsApp already live in Slack and are not a dedicated support team: sales, customer success, operations, a founder following a client group. For them, opening one more tool is why messages go unanswered.

When there is a support team with a queue, metrics and several people answering all day, a support inbox usually works better than a Slack channel. If your team already uses Crisp, see Crisp WhatsApp integration, where each group becomes one conversation in the inbox.

How does the BatZap Slack integration work?

BatZap is a team inbox for WhatsApp, with 1:1 chats, groups and broadcasts in one place, and it integrates with Slack. The idea is to bring what happens on WhatsApp into the channel your team already watches, with replies synced both ways: what the team answers in Slack reaches WhatsApp.

What it does today:

Inside BatZap, group management is the strong part: create groups from the dashboard, add and remove participants, promote admins, see each participant by name and number, assign a group to one or more people, set status, tags and notes. Backup numbers join as group admins, so if the main number goes down, the group is not lost.

The honest trade-off: a QR-code connection is not immune to bans. BatZap is built for conversations, not campaigns, which avoids the usage patterns that usually trigger bans, and backup numbers protect your groups. Even so, the number still follows WhatsApp's rules.

Step by step: connect WhatsApp to Slack with BatZap

1. Create your account and start the 14-day trial at batzap.com (card required).
2. Connect your number by scanning the QR code with WhatsApp on your phone. You keep the number you already use.
3. Add a backup number so it joins your groups as admin.
4. Connect Slack and authorize BatZap in your workspace.
5. Test both directions: send a message from someone else's phone, see it arrive in the channel and reply from Slack.

Summary: which WhatsApp Slack integration should you pick?

If you only want a Slack alert when a message arrives, Zapier or Make do it cheaply, as long as you accept replying outside Slack or building the return path by hand. If you need to reply from Slack, QR-code options such as 2Chat and BatZap do it today. For large groups, remember that the official API caps groups at 8 people.

BatZap's difference is that Slack is one end of a full group operation: create, moderate, assign and protect groups with backup numbers, priced per plan rather than per seat. If that is your case, try BatZap free for 14 days and connect your WhatsApp to Slack today.

Frequently asked questions

Can I integrate WhatsApp with Slack for free?

Yes, with limits. Zapier's free plan allows 100 tasks a month on two-step Zaps, and Make's free plan gives 1,000 credits a month. That covers message alerts at low volume. Replying from Slack to WhatsApp needs a second automation and, on the official API, Meta charges per message sent.

Does Slack have an official WhatsApp app?

No. As of October 2026, Slack has no native WhatsApp integration, and Meta does not publish an official Slack app. Every option is third-party: automation platforms like Zapier and Make, apps that connect your number to Slack, or your own integration built on a WhatsApp API.

Can I reply to a WhatsApp group from Slack?

Yes, but only with tools that read groups and sync both ways. Meta's official API caps groups at 8 participants and requires a verified account, so teams that run communities use tools that connect the number by QR code. Check during the trial that a thread or channel reply reaches the right group.

Does a WhatsApp Slack integration increase the risk of a ban?

The integration itself does not; usage does. QR-code tools use your regular number, which can be banned if the pattern looks like spam, such as sending many identical messages to people who did not ask. Replying to existing chats and groups is normal use. Backup numbers limit the damage if the main one goes down.