How to Integrate monday.com With WhatsApp Business: A Step-by-Step Guide
Somebody asks for this almost every week: "can we get WhatsApp messages into monday.com?" The answer is yes — but the honest first step is explaining what that actually means, because monday.com doesn't have a WhatsApp button built into the core platform. There's no toggle in Settings that just turns this on.
What exists instead are a few different paths that all connect the two, each with a different amount of setup and a different price tag. Here's what actually happens behind each one, so you pick the right one instead of the first one that shows up in a Google search.
Why There's No "Just Click Connect" Button
WhatsApp doesn't hand out open access to its messaging network. Businesses reach customers on WhatsApp through the WhatsApp Business Platform (formerly the Cloud API), which requires an approved sender, message templates reviewed by Meta, and a technical layer that receives and sends messages on your behalf. monday.com — like almost every other business tool that "integrates with WhatsApp" — sits on the other side of that layer, not directly wired into WhatsApp's servers.
That layer is the part that actually varies between solutions. It's worth understanding before picking one.
The Three Real Paths
Path 1: A marketplace app built for this. monday's app marketplace has WhatsApp integration apps built by partners, mostly aimed at monday CRM. They handle the Meta approval and template management for you, and give you monday-native building blocks: triggers like "when a new WhatsApp message arrives, create an item," and actions like "when status changes, send a WhatsApp template." This is the least technical path and the fastest to working. The trade-off is you're depending on that app's uptime and pricing, on top of your monday.com subscription.
Path 2: No-code middleware — Make, Zapier, or n8n. These platforms already have both monday.com and WhatsApp Business connectors built. You build the logic yourself: "new item in this board → send this WhatsApp template to this number," or "incoming WhatsApp message → create an item in this board with this content." More flexible than a marketplace app, because you're not limited to what one app's builder decided to support. Also more setup work, and pricing is usually per operation or per task run, which adds a cost that scales with volume.
Path 3: Direct WhatsApp Business Platform + webhooks. For teams with a developer, or high enough volume that per-operation middleware pricing stops making sense. You register directly with Meta, get your own approved sender, and write the logic that maps monday.com events to WhatsApp API calls and back. Full control, no per-task fees to a third party — and full responsibility for maintaining it, handling Meta's template approval process yourself, and keeping the integration running when either platform changes its API.
Setting It Up: The Make.com Path (Most Common for Growing Businesses)
This is the path that fits most of the businesses we work with — flexible enough to be useful, without needing a developer on staff. Here's the shape of it:
Get WhatsApp Business Platform access. This happens through a Meta Business Manager account and a Business Solution Provider (BSP) — Make and similar platforms partner with BSPs so you don't deal with raw Meta infrastructure directly. This step, not the automation itself, is usually where the timeline lives: template approval can take a few days.
Connect both apps in Make. Add monday.com and WhatsApp Business Cloud as connections, authenticating each with the relevant account credentials.
Build the inbound scenario. Trigger: new WhatsApp message received. Action: create an item on your leads board, mapping the sender's number and message text into the right columns.
Build the outbound scenario. Trigger: status changes to something specific (Proposal Sent, say). Action: send an approved WhatsApp template to the contact number stored on that item.
Add the safety net. A scenario that checks for items where a WhatsApp lead came in and nobody responded within, say, two hours, and notifies the assigned rep. This is the piece that actually prevents leads from going cold — and it's a monday.com automation you already know how to build once the item exists on the board.
Test with real numbers before rolling out. Template messages have to be pre-approved by Meta and can't be edited on the fly, so confirm the wording is right before it's the thing forty leads receive.
(This is the same "when this happens, do that" logic behind every automation on your boards — see: 5 monday.com Automations That Save Your Team Hours Every Week)
What Nobody Mentions: Template Rules
The part that trips people up isn't the automation logic — it's WhatsApp's own rules about what you're allowed to send. Businesses can't just message anyone who once texted them; messages sent outside a 24-hour window since the customer's last message have to use a pre-approved template, categorized as Utility, Marketing, or Authentication. A payment reminder and a promotional offer are different categories with different approval requirements.
Practically: get your core templates (new lead acknowledgment, appointment reminder, follow-up nudge) submitted for approval early, because that review happens on Meta's timeline, not yours.
Being Honest About the Cost
This isn't free, and it isn't a single number. You're stacking your monday.com plan, a Make or Zapier subscription (or a marketplace app's fee), and WhatsApp's own conversation-based pricing, which varies by country. For a small team getting started, that stack can run somewhere in the $50–150/month range beyond what you already pay for monday.com — before factoring in setup time.
Where it earns that back: WhatsApp's open rates dwarf email's, and for a Mexican SMB audience in particular, WhatsApp is often the channel customers actually check. If your leads are currently going cold in an inbox, this is usually a faster payback than it looks on paper. If your team gets three WhatsApp inquiries a month, it's very likely not worth the setup yet — a person answering messages directly still works fine at that volume.
Ready to Connect the Channel Your Customers Actually Use?
The mechanics here aren't complicated once they're mapped out — the part worth getting right is the template approval and the safety-net automation, since those are what determine whether this actually saves time or just adds a new place for leads to get stuck.
