HubSpot
The WhatsApp conversation, on the HubSpot record.
Connect the portal once. People are matched by phone number, messages land on the contact timeline as communications, and deals stay in step — each behind its own switch.
HubSpot has every email. It has never seen the WhatsApp.
Your team closes on WhatsApp and reports out of HubSpot, so the record shows a call, three emails and a gap where the actual conversation was. The next person to open that contact reads a story with the middle missing — and asks the customer to repeat it.
Connect the portal, then choose what syncs
An OAuth install from Settings, by an owner or admin. Nothing moves on its own: messages and deals are separate switches and both start off.
People matched on the number, not the formatting
HubSpot holds +971 50 123 4567 and WhatsApp holds 971501234567. The last ten digits are compared across both the phone and the mobile field, so the contact you already have is found rather than duplicated.
A communication, not a robot note
Messages are written as HubSpot communications with the WhatsApp channel and the direction set. They render in the activity feed and your reports can count them — which a note left by an integration never can.
Deals kept in step, not posted twice
Switch deals on and a deal from the inbox pipeline is created once, then updated in place every time it moves. It carries the title, the value and the stage.
The thread inside the contact record
A card on the HubSpot contact shows the recent WhatsApp messages for that person, so somebody working in HubSpot reads the conversation without changing tab.
What crosses over
- Real inbound and outbound WhatsApp messages, on the matched contact.
- A contact created in HubSpot when the number is one your portal did not have.
- Deals from the inbox pipeline — title, value and stage — once you switch deals on.
What never does
- Internal notes. Checked before every other preference: a note is what your team writes when the customer must not see it, and a CRM timeline is somewhere their staff read daily.
- Private conversations, and numbers somebody excluded. The sync sits below the privacy check rather than beside it, so it is unreachable rather than filtered.
- Label changes, delivery receipts and read state. A timeline is not a log.
Integrations are a Pro capability. Starter does not include HubSpot, Pipedrive, Zapier, webhooks or the API.
When you would use it
- A salesperson leaves and the deal history goes with their phone.
- A HubSpot workflow that should fire when a WhatsApp enquiry turns into a quote.
- Reporting that counts calls and emails and quietly ignores the channel that closed the deal.
- Somebody working in HubSpot needing to read what was said without asking on Slack.
What this leans on
Questions people ask
Which plan is this on?
Pro. Integrations — HubSpot, Pipedrive, Zapier, webhooks and the API — are a Pro capability, and Starter does not include them.
Will it flood the timeline?
Only if you ask it to. You can sync incoming messages only, and you can restrict the whole connection to conversations carrying particular labels, so a support queue need never reach the CRM.
What does it ask HubSpot for?
Read and write on contacts and deals, and nothing else. Every scope on the install screen is exercised by the sync — an integration asking for permissions it never uses is how a security review stalls.
Can a HubSpot stage drive the inbox?
Not today. This writes to HubSpot rather than reading back from it. Stage ids are per portal and per pipeline, so rather than guess at a mapping, the inbox stage is written where a HubSpot workflow can read it.