How to Connect WhatsApp to HubSpot: Native and API Options

You can connect WhatsApp to HubSpot in three ways: HubSpot’s own WhatsApp channel, a WhatsApp inbox tool that ships a native HubSpot integration, or a shared inbox such as whatsappx.si that forwards each incoming message to a webhook so your own code can write it into HubSpot. This guide explains what each option does, what it requires, and how to build the webhook route step by step.

What should a WhatsApp–HubSpot integration actually do?

Before comparing tools, write down what “integrated” means for your team. Most sales and support teams want four things:

The first three can be done with any route in this guide. The fourth, sending from inside HubSpot, is only native in HubSpot’s own channel and in tools that built a two-way connector.

What native WhatsApp options does HubSpot offer?

HubSpot sells a WhatsApp channel for its conversations inbox and help desk. The facts below come from HubSpot’s own documentation (last updated July 21, 2026, checked as of October 2026) (Connect a WhatsApp channel to the conversations inbox).

• Subscription: available with Marketing Hub Professional or Enterprise, or Service Hub Professional or Enterprise. HubSpot’s product page says the same: it requires “Professional or Enterprise versions of Marketing Hub or Service Hub, as well as a WhatsApp business account and phone number” (HubSpot WhatsApp integration page).
• Account type: “Due to Meta’s requirements for using the WhatsApp integration, you cannot connect a personal WhatsApp account to HubSpot and must connect a Business account instead.” The number runs on Meta’s WhatsApp Business Platform, which means Meta’s per-message pricing applies (Meta pricing).
• History: “Only new messages after you connect your WhatsApp Business Account will sync to HubSpot. Historical conversations will not be synced.”
• Where messages live: once connected in the standard way, messages “will no longer appear in the WhatsApp mobile app or web app, and will only appear in the conversations inbox.” Messages are logged on the contact’s activity timeline when the phone number matches a contact record.
• Templates and the 24-hour window: business-initiated conversations need a pre-approved template, sessions stay open for 24 hours after the contact’s last reply, and HubSpot caps template messages at 1,000 per month, shared by all connected WhatsApp business accounts.

What about keeping the number in the WhatsApp Business app?

HubSpot also documents a coexistence setup that lets you “use the same WhatsApp Business phone number in both the WhatsApp Business App and HubSpot at the same time.” It needs Super Admin rights in HubSpot and admin access to Meta Business Manager, and the number must already be registered in the WhatsApp Business app on your phone. HubSpot “automatically imports past conversation history from the last 180 days,” although images and videos are not backfilled, voice notes cannot be sent from the HubSpot inbox, and sending is capped at 20 messages per second (Connect a WhatsApp number to HubSpot using coexistence). The 20-messages-per-second cap and the roughly six months of history match Meta’s own description of coexistence (Meta: onboarding WhatsApp Business app users).

HubSpot’s App Marketplace lists third-party apps as well, for example a browser extension that shows the matched HubSpot contact, deals and tickets beside WhatsApp Web (Salesmsg for WhatsApp Web listing). Those apps have their own terms and pricing, so check each listing.

Which WhatsApp inbox tools offer HubSpot integrations?

Several WhatsApp team-inbox products list a HubSpot integration on their own websites as of October 2026. This matters if you want a ready-made integration rather than code. Check each vendor’s current plan details, because what is included can change:

These tools are stronger than whatsappx.si on this specific point: they have done the HubSpot work for you. The sections below are for teams that use whatsappx.si for its shared inbox and want HubSpot to see those conversations too.

Where does whatsappx.si fit?

whatsappx.si is a shared WhatsApp inbox for teams. You scan a QR code to connect the WhatsApp you already have (it becomes a linked device, like WhatsApp Web, and recent chat history syncs in), and your whole team replies from one inbox, with chat assignment and keyword-triggered auto-replies. AI replies are coming soon and are not available yet. If you need it, you can also connect a number through Meta’s official WhatsApp Business Platform with Embedded Signup.

To be clear: whatsappx.si does not have a built-in HubSpot integration. What it has is a developer layer:

• Outbound webhooks. whatsappx.si POSTs inbound WhatsApp events to each enabled HTTPS URL you register. For a QR-linked number, each incoming customer message is sent as a whatsappx.si JSON payload; for an official-platform number, Meta’s webhook payload is forwarded as received. Each delivery carries an X-Hub-Signature-256 header (sha256= followed by a hex HMAC-SHA256 of the body, keyed with the secret shown once when you create the webhook), an optional X-Whatsappx-Webhook-Token header if you configured a token, and an X-Whatsappx-Event header set to scan.whatsapp for QR-linked numbers or meta.whatsapp for official-platform numbers.
• A REST API under /api with API keys (Authorization: Bearer …) and an X-Tenant-ID header for the workspace. It lists conversations and messages, starts a conversation by phone number, sends a text message in an existing conversation, and lists, adds and deletes contacts.
• In-app API docs that document every endpoint and payload, plus a live event stream.

That is enough to log WhatsApp conversations into HubSpot with a small service you host. It is not a two-way connector, so reps still reply from the whatsappx.si inbox, not from HubSpot.

How do you connect whatsappx.si to HubSpot with webhooks and the API?

The recipe is: whatsappx.si webhook → your receiver → HubSpot CRM API. Here is the sequence.

1. Create a HubSpot private app with the crm.objects.contacts.read and crm.objects.contacts.write scopes (the notes API uses the same scopes), and copy its access token (HubSpot Contacts API, HubSpot Notes API).
2. In whatsappx.si, open Workspace settings → Outbound webhooks (workspace admins) and add your receiver’s HTTPS URL. Save the signing secret; it is shown only once. Optionally generate a delivery token as a second check.
3. Deploy a receiver that verifies the signature, acknowledges quickly, then finds or creates the contact in HubSpot and logs the message as a note.
4. Send yourself a test WhatsApp message and confirm a note appears on your own contact record.

The outline below uses Node.js. Payload fields are listed in the in-app API docs; the pickFields function is where you map them. QR-linked deliveries include fields such as chat_phone and content, while official-platform deliveries follow Meta’s own webhook format.

// Outline only. Verify the exact signature encoding and payload fields
// in the whatsappx.si in-app API docs before going live.
import crypto from 'node:crypto';
import express from 'express';

const app = express();
app.use(express.raw({ type: 'application/json' }));

const safeEqual = (a, b) =>
  a.length === b.length && crypto.timingSafeEqual(Buffer.from(a), Buffer.from(b));

app.post('/whatsappx', async (req, res) => {
  // 1. Verify the HMAC-SHA256 signature with the secret shown at create.
  //    The header value looks like "sha256=<hex digest>".
  const expected = 'sha256=' + crypto
    .createHmac('sha256', process.env.WX_WEBHOOK_SECRET)
    .update(req.body)
    .digest('hex');
  if (!safeEqual(req.get('X-Hub-Signature-256') || '', expected)) return res.sendStatus(401);
  if (process.env.WX_WEBHOOK_TOKEN &&
      req.get('X-Whatsappx-Webhook-Token') !== process.env.WX_WEBHOOK_TOKEN) {
    return res.sendStatus(401);
  }

  // 2. Acknowledge first; whatsappx.si retries briefly on failures.
  res.sendStatus(200);

  const event = JSON.parse(req.body.toString());
  const source = req.get('X-Whatsappx-Event'); // 'scan.whatsapp' or 'meta.whatsapp'
  const { phone, text } = pickFields(source, event); // e.g. chat_phone + content for scan.whatsapp
  if (!phone || !text) return; // skip events with no customer message, such as Meta status updates

  // 3. Find or create the HubSpot contact by phone.
  let contactId = await hubspotSearchContactByPhone(phone);    // HubSpot CRM search API
  if (!contactId) contactId = await hubspotCreateContact(phone); // HubSpot contacts API

  // 4. Log the message as a note associated with the contact.
  await hubspotCreateNote({                                    // HubSpot notes API
    contactId,
    hs_timestamp: Date.now(),
    hs_note_body: '[WhatsApp via ' + source + '] ' + text,
  });
});

Two HubSpot details worth knowing: the notes endpoint requires hs_timestamp, which “determines where the note sits on the record timeline,” and a note is attached to a contact by including an associations object in the request (HubSpot Notes API). Searching contacts by phone goes through HubSpot’s CRM search endpoint, and phone is one of its default searchable properties (HubSpot CRM search).

Can you go the other way, from HubSpot to WhatsApp?

Partly. If your HubSpot subscription lets workflows send webhooks, a workflow can call your receiver, which can then call the whatsappx.si API to start a conversation by phone number or send a text in an existing one. Treat this with care. WhatsApp says its products are not intended for automated messaging, so do not let workflows trigger messages from a QR-linked number; a person on your team should send those from the inbox. Workflow-triggered messages belong on an official-platform number, with approved templates, and only to people who opted in and expect the message.

Which option should you choose?

What number-safety rules apply when you connect WhatsApp?

Integrations make it easy to send more than you should. WhatsApp states that its products “are not intended for bulk or automated messaging,” and its Business Messaging Policy allows you to contact people only when they gave you their number and opted in (WhatsApp Help Center, WhatsApp Business Messaging Policy). Breaking those rules can lead to temporary or permanent restrictions, including on linking devices (WhatsApp Help Center).

Before you connect a number by QR code, and before you send anything prompted by HubSpot data:

• Let a new number mature. Use a brand-new WhatsApp number normally for 15–20 days (real conversations, both directions) before you connect it.
• Send in small batches. 5–10 messages at a time, never a bulk blast, and leave gaps between batches.
• Only message people who opted in and stop when they ask you to.
• Use the official platform for volume. Templates, automation at scale and higher throughput belong on Meta’s WhatsApp Business Platform, not on a linked device.

What privacy obligations apply when WhatsApp chats land in HubSpot?

Copying chat content into a CRM creates a new record of personal information, and in the US that brings state privacy law into play. A few points for teams in or selling to California:

• B2B contacts count. The CCPA’s exemptions for business-to-business personal information expired on December 31, 2022, so the names, numbers and chat content of business contacts are in scope (California AG: CCPA).
• Notice at collection. Your notice must state the categories and purposes of collection and “the length of time the business intends to retain each category of personal information,” or the criteria used to decide it (Cal. Civ. Code 1798.100). Decide how long WhatsApp notes stay in HubSpot and say so.
• Service-provider contracts. Every vendor that processes the data for you, including whatsappx.si, HubSpot and your hosting provider, should be under a contract that limits use to the named business purposes (CPPA regulations).
• Say what you do. The FTC expects companies to live up to their privacy promises, so keep your policy accurate about which numbers are QR-linked and which go through Meta’s platform (FTC business guidance). For official-platform numbers, Meta acts as a processor on your behalf and keeps messages for a maximum of 30 days (Meta: data privacy and security).

For example, a home-services company could log only the customer’s first message and the booking confirmation to HubSpot, keep full transcripts in the inbox, and set a 12-month retention rule on both. That keeps the CRM useful without duplicating every chat.

How do you get started?

If you qualify for HubSpot’s native channel and want reps replying from HubSpot, start there. If your team works from a shared WhatsApp inbox, create a whatsappx.si workspace, connect your number by QR code or through the official platform, add an outbound webhook under Workspace settings, and point it at a receiver like the one above. Then send one test message and watch it arrive on your HubSpot timeline.