WhatsApp Business API Integrations: CRM, Shopify, Helpdesk and ERP

Once WhatsApp becomes a real sales and support channel, the next question is always the same: can it talk to the tools we already use? The CRM that holds your leads, the store that holds your orders, the helpdesk that holds your tickets. The answer is usually yes — but the route differs for every product, and the differences decide what you pay, where your team works and who controls the number. This guide goes product by product, using each vendor's own documentation.

How WhatsApp integrations actually work

Every integration sits on Meta's WhatsApp Business Platform. A business tool reaches WhatsApp in one of four ways:

1. A native channel built by the tool itself. HubSpot, Salesforce, Zoho CRM and Zendesk all offer one. You connect your number through Meta's sign-up inside their settings, and conversations live in their inbox.
2. A marketplace app from a WhatsApp provider. A provider's app on the Shopify App Store, HubSpot App Marketplace or Salesforce AppExchange syncs contacts and messages between its platform and the tool.
3. A no-code connector such as Zapier or Make, which moves data between apps on triggers you define.
4. A custom build on the Cloud API, written by your developers or an agency.

WhatsApp Business API integration with CRM

A CRM integration is usually about two things: every WhatsApp conversation appearing on the right contact or deal, and being able to send a template from a record — a quote follow-up, a payment reminder, a demo confirmation — without leaving the CRM.

WhatsApp Business API HubSpot integration

HubSpot has a native WhatsApp channel for its conversations inbox and help desk. According to HubSpot's knowledge base, connecting it requires a Marketing Hub or Service Hub Professional or Enterprise subscription, a Meta business account you administer and a phone number that can receive voice calls. Incoming messages are associated with contacts whose stored phone number matches and appear on the contact's timeline; unmatched ones show as unknown visitors. HubSpot sets a shared limit of 1,000 template messages a month across connected WhatsApp accounts, and supports coexistence with the WhatsApp Business app.

Businesses on lower HubSpot tiers, or those who need more template volume, typically use a WhatsApp provider's app from the HubSpot App Marketplace instead. Check that any app you pick uses the official WhatsApp Business Platform, not WhatsApp Web automation.

WhatsApp Business API Salesforce integration guide

Salesforce offers WhatsApp in two places. In Service Cloud, an admin turns on Messaging in Setup and creates an enhanced WhatsApp channel; each channel is linked to a WhatsApp Business Account, which the setup walks you through creating. Salesforce lists WhatsApp messaging under Contact Center Digital, sold as an add-on to Service Cloud editions. In Marketing Cloud Engagement, WhatsApp is sold as a separate SKU and used for templated, journey-driven messages.

A practical Salesforce plan looks like this:

1. Decide whether WhatsApp is a service channel (Service Cloud), a marketing channel (Marketing Cloud) or a sales channel — the licences differ.
2. Confirm with your Salesforce account executive which add-on your org needs, and its cost.
3. Prepare a verified Meta business portfolio and a number not in use on another platform.
4. Map which object each conversation should land on — contact, lead, case — and who routes it.
5. If the native route does not fit, compare WhatsApp apps on AppExchange, checking each uses the official Business Platform.

Zoho CRM

Zoho CRM's Business Messaging connects WhatsApp through Meta's embedded sign-up and, per Zoho's help centre, is available on the trial and all paid editions. You can send approved templates from lead and contact records, trigger them from Workflow Rules, Blueprints and Journeys, and reply to customer-started conversations in the Messages module within the 24-hour window.

WhatsApp Business API integration with Shopify

Shopify connects to WhatsApp in two ways. Shopify Messaging, Shopify's own marketing app, can send WhatsApp marketing campaigns to subscribers from the Shopify admin, charged per message on your Shopify bill; India is among the supported regions. For everything else — order confirmations, shipping updates, cash-on-delivery confirmation, two-way chat — merchants install a WhatsApp app from the Shopify App Store, most of them built by WhatsApp providers.

What typically flows: order placed, fulfilled and delivered events from Shopify become utility templates to the customer; the customer's name, order number and tracking link fill the template variables; replies come back to the provider's inbox. When choosing an app, check that it states it uses the official WhatsApp Business API, whose number and Meta account it uses, and how its message prices compare with Meta's.

WhatsApp API integration for ecommerce checkout

Checkout is where WhatsApp earns its keep for online stores, in three places:

• Opt-in at checkout. A clearly worded checkbox next to the phone field is the cleanest way to collect WhatsApp consent. See WhatsApp opt-in rules.
• Abandoned checkout reminders. Shopify's Admin API exposes abandoned checkouts — those where the customer entered contact details but did not pay — along with a recovery link. An app or integration sends a template with that link. Because a reminder encourages a purchase, expect it to be treated as a marketing message, priced accordingly.
• Payment inside the chat. Meta's Payments API for India lets a business send an order-details message and collect payment through a configured Razorpay or PayU gateway, or through UPI. This needs development work or a provider that supports it.

WooCommerce and other store platforms follow the same pattern through plugins or webhooks. Whatever the platform, keep order updates free of promotional content so they stay in the cheaper utility category — see message templates.

Connect WhatsApp Business API to your existing helpdesk

For support teams, the helpdesk is usually the right home for WhatsApp conversations: each chat becomes a ticket with the same routing, SLAs, macros and reporting as email. Before you connect, check the helpdesk's plan requirements for its WhatsApp channel, how it handles the 24-hour window (replying after it closes needs a template), whether agents can send templates from a ticket, and whether it can take over a number you already use with another provider.

WhatsApp Business API integration with Zendesk

Zendesk has a native WhatsApp channel, added by an admin as a messaging channel in the Agent Workspace. Zendesk's help centre says the person connecting it must be an admin of your own Meta Business Manager, and the number must be able to receive international calls or SMS. Numbers already connected through another Business Solution Provider can be migrated to Zendesk. WhatsApp conversations then arrive as messaging tickets, and Zendesk documents workflows for proactive messages to users. Check Zendesk's current plan and add-on requirements for your account before you start, as they vary by product edition.

WhatsApp Business API integration with an ERP system

ERP integrations are about documents: sending an invoice, a quotation, a delivery challan or a payment reminder to the customer on WhatsApp the moment it is created. Odoo has its own WhatsApp app, available on Odoo Enterprise, that uses the WhatsApp Business Platform with credentials from your own Meta developer app; templates can be linked to records such as quotations, invoices and event tickets.

Most ERPs used by Indian businesses do not have a WhatsApp channel of their own. The usual routes are a provider's plugin built for that ERP, a no-code connector, or a small custom service that watches for new invoices and calls the Cloud API. Whichever you choose, agree on which ERP events send a message, which template each uses, and how the customer's reply reaches a human.

No-code connectors and custom builds

Zapier has a WhatsApp Business app with triggers for new incoming messages and message status updates, and actions to send free-form, media and template messages. Make has a verified WhatsApp Business Cloud app maintained by Make, with modules to send messages and templates and a webhook trigger. Both connect directly to your Meta account, which suits simple flows — a new CRM lead gets a welcome template, a form submission creates a contact — without a developer.

When the flow is business-critical, involves many systems or needs precise control over retries and data, a custom build on the Cloud API is the dependable route: your service sends messages through Meta's API and receives replies and delivery statuses on a webhook. Our WhatsApp Cloud API developer guide covers the setup, tokens and webhooks.

Where wbm.link fits today

wbm.link does not have native integrations with any CRM, store, helpdesk or ERP yet, and it has no public API, webhooks or Zapier or Make connector. Teams that use it treat it as their WhatsApp inbox: the whole team replies from one shared inbox, sends templates and broadcasts to labels or CSV-imported contacts with custom fields, and runs keyword replies, a flow chatbot and an AI assistant. Contacts move between wbm.link and other systems by CSV export and import. If your process depends on WhatsApp messages syncing automatically into a CRM or helpdesk, one of the routes above will serve you better today.

Before you connect anything: a checklist

• Where do replies happen? Pick one home for conversations; a number is normally connected to one platform.
• Whose Meta account is it? Connect through your own business portfolio so the number stays yours.
• What does it cost in total? The tool's plan or add-on, any app fee, and message charges — on whose invoice.
• Which data moves, and which way? Contacts, opt-in status, order or ticket IDs, conversation history.
• Is consent recorded? Every integration that sends templates needs opt-in captured somewhere it can check.
• What happens when it fails? A failed template or expired token should alert someone, not fail silently.