HubSpot WhatsApp integration: connect WhatsApp to HubSpot

WavesFlo connects to HubSpot natively: sign in to HubSpot from Integration, then CRM, and once a workspace admin turns syncing on, one-to-one WhatsApp chats and opt-outs on your linked numbers are logged as notes on the contact with the matching phone number. Group messages never reach HubSpot. HubSpot's own WhatsApp channel and an n8n workflow are the alternatives. For wider team roll-outs with role-based access and SSO see Enterprise; the FAQ covers pricing and the common setup gotchas.

All three routes are below: what WavesFlo's integration logs and leaves out, what HubSpot's channel needs, including its option for keeping a number on the WhatsApp Business app, the n8n workflow for tasks and custom steps, how to avoid duplicate contacts, and what belongs in each tool.

Does WavesFlo connect to HubSpot natively?

Yes. Connect HubSpot from WavesFlo's dashboard, under Integration, then CRM, by signing in to HubSpot. Every sync switch starts off, and nothing reaches HubSpot until a workspace admin turns one on.

• Incoming one-to-one messages, outgoing one-to-one messages, and opt-outs and opt-ins each have their own switch, and each is logged as a note on the matching contact.
• Matching is by phone number: a remembered link first, then HubSpot's own phone search, then a new contact only if the connection is allowed to create one.
• Group, status and channel messages never reach HubSpot. Media isn't copied: the note says a photo or document was sent. Very long messages are cut at about 4,000 characters.
• HubSpot contacts with a usable international phone number can be imported into WavesFlo's audience, on demand or every six hours, without duplicates. An import never records consent, because being in HubSpot isn't agreeing to WhatsApp messages, so imported people start with unknown consent.
• Disconnecting revokes WavesFlo's access in HubSpot.

Does HubSpot have a WhatsApp integration?

Yes. HubSpot connects a WhatsApp Business account as a channel in its conversations inbox, set up from Settings, then WhatsApp, through a Meta sign-in window. Its help pages, updated in July and September 2026, say:

• The channel is listed for Marketing Hub and Service Hub, Professional or Enterprise. Connecting needs admin rights on your company's Meta Business Manager.
• A standard connection needs a number that can receive voice calls and isn't connected to another WhatsApp account, the WhatsApp Business app or another integration. Once connected, its messages appear only in HubSpot, not in the phone apps, and earlier conversations aren't synced.
• Coexistence keeps the number on the WhatsApp Business app as well. A HubSpot Super Admin connects it, you scan a QR code shown in HubSpot with the app, messages sync both ways, and the last 180 days of conversations are imported, with photos and videos as placeholders. Voice notes can't be sent from HubSpot.
• Each WhatsApp Business account can hold up to 25 numbers, and 1,000 pre-approved messages a month are shared across all connected accounts. More than 50 business-started conversations a day needs a verified Meta Business Manager.
• Replies are free-form for 24 hours after the contact's last message; after that, only a pre-approved message can reopen the conversation.
• A message from a number that exactly matches a contact's Phone number or Mobile phone number joins that contact's timeline. Anything else shows as an Unknown visitor until someone links it.

Which route suits a sales team?

Choose HubSpot's channel if you already pay for Marketing Hub or Service Hub Professional and want reps to work inside HubSpot. WavesFlo's integration suits teams whose leads arrive on reps' own numbers and who want those chats in a shared inbox with assignment and roles while HubSpot keeps the record. Add the n8n workflow when you also want a task for the owner, custom fields, or a message sent when a HubSpot property changes. Power Automate users will find HubSpot connectors in Microsoft's catalogue, but as of October 2026 they come from an independent publisher and are in preview, and the CRM one is Premium.

How do you send WhatsApp leads to HubSpot with n8n?

1. 1In HubSpot, create a service key with the scopes n8n's credential page recommends for the HubSpot node, including read and write access to contacts, and paste it into an n8n HubSpot credential. n8n's documentation recommends service keys as of October 2026, while noting they are in public beta; OAuth2 also works with the HubSpot node.
2. 2Start with a Webhook node whose URL WavesFlo sends message events to, and verify each delivery's signature, as the webhooks guide shows. Then add an If node that passes message.received from direct chats only, and a Remove Duplicates node keyed on the event ID, because a delivery can arrive twice.
3. 3In an Edit Fields (Set) node, put the sender's number in one format, such as +919876543210, and keep the profile name, the message, the time and the number it arrived on.
4. 4Add the HubSpot node with Contact and Search contacts: one filter group for Phone Number equal to the sender's number, and a second for Mobile Phone Number. Separate filter groups are combined with OR.
5. 5If nothing matches, create the contact. The node's Create/Update a contact asks for an email address, which WhatsApp leads rarely give, so use an HTTP Request node with Predefined Credential Type and your HubSpot credential to call HubSpot's contacts API. It needs only one of email, first name or last name, so the profile name and the phone number are enough.
6. 6Log the message. The HubSpot node can create Call, Email, Meeting and Task engagements, so a task for the contact's owner, such as Reply to new WhatsApp enquiry, needs no code. For the message text itself, add a note through HubSpot's notes API with another HTTP Request node; a note needs a timestamp and holds up to 65,536 characters.
7. 7Test from your own phone, then publish the workflow.

The workflow records; it doesn't reply. Answers go out from the inbox, on the number the chat came in on, and an unchecked webhook URL would let anyone who finds it create contacts, which is why the signature check comes first.

How do you stop duplicate contacts in HubSpot?

HubSpot's developer documentation calls email the primary unique identifier for avoiding duplicate contacts, and WhatsApp leads arrive with a number instead. So the workflow has to do the matching:

• Deduplicate deliveries on the event ID before the search runs.
• Store every number in one format, and tidy existing contacts once. A number saved as 098765 43210 may not match +919876543210, and HubSpot's own channel also needs an exact match.
• Search both Phone Number and Mobile Phone Number before creating anything.
• Expect the occasional pair when a brand-new lead sends two messages seconds apart and both runs search before either creates. Merge it in HubSpot when it appears.

What should go into HubSpot, and what stays in WhatsApp?

HubSpot holds the record: the contact, owner, deal stage, tasks and reports. WavesFlo holds the conversation: every number's chats in one inbox, where people assign chats, add internal notes and set labels. WavesFlo isn't a CRM and has no pipeline or lead scoring. Its HubSpot integration logs notes on contacts once an admin turns syncing on, while owners, deal stages and tasks stay in HubSpot; an n8n workflow can add a task for each new lead. Switch on outgoing messages only if someone will read the timeline, because a chatty customer can add dozens of notes a day.

For the rest of the routine, see WhatsApp lead management and WhatsApp for sales teams. The same events can write to a Google Sheet; Zoho CRM connects natively, like HubSpot; and the event reference is on the developers page.