Whatsable
Connect HubSpot to WhatsApp. Properly.
HubSpot’s WhatsApp story is real. It’s also partial. Most teams searching “HubSpot WhatsApp integration” end up at the native channel, find it useful for one job, and miss the other half of what they actually need.
This post is the full picture. What HubSpot does natively. What it doesn’t. The 4-step setup that fills the gap. The 6 workflows worth shipping first. And the HubSpot-specific gotchas that quietly break setups when you don’t know about them.
What HubSpot does natively
HubSpot’s native WhatsApp channel gives you a multi-rep inbox tied to your business number. It’s well-built:
- Inbound customer messages land in the conversations inbox
- Multiple reps can reply from inside HubSpot, no phone-switching
- Inbound conversations log to the contact record automatically
- The native inbox supports media, replies, and the standard agent assignment patterns
For inbound handling, this is the right primitive. Use it.
What’s missing
The native channel is an inbox. It is not an action layer.
Specifically, three things HubSpot’s native side doesn’t do:
1. Workflow-fired templated outbound. You can’t build a workflow that says “when lifecycle stage moves to Marketing Qualified Lead, fire a WhatsApp template named lead_acknowledgement to the contact’s phone, populated with their first name and company.” The native side doesn’t expose that action.
2. Multi-number routing. If you operate multiple WhatsApp numbers - per region, per team, per business unit, per portal - the native channel ties one number to one HubSpot instance. Routing logic across numbers isn’t there.
3. Template management UX. Submitting templates for Meta approval, watching their status, getting notified of rejections - that whole workflow lives outside HubSpot and isn’t surfaced inside the native channel UI.
Fix all three by sending through Whatsable from a HubSpot webhook, via Zapier, Make, or n8n, on the same business number. Combined with HubSpot's native inbox, the setup is two-way.
The 4-step setup
Step 1: Connect your business number through a Meta Tech Provider
(~5 min Meta verification flow inside the provider's console)
Step 2: Approve 6 templates in the provider's dashboard:
lead_acknowledgement, quote_followup, ticket_status_update,
renewal_outreach, rep_internal_alert, deal_won_thankyou
Step 3: In HubSpot, add a workflow webhook. Point it at a catch URL from Zapier, Make, or n8n — whichever you already use. That tool then asks Whatsable to send the WhatsApp message.
Step 4: Build your first workflow — usually Lifecycle Stage = MQL. Keep HubSpot's native inbox for replies if you already use it. Or have Zapier, Make, or n8n update the contact when a reply comes back through Whatsable.
Half a day total, mostly Meta template review time (24-48 hours) you can spend doing other work.
Whatsable is an official Meta Tech Provider. There is no Whatsable app in HubSpot, and no HubSpot workflow step that sends WhatsApp on its own. HubSpot fires a webhook. Zapier, Make, or n8n catch it. Whatsable sends the message. That is the path the rest of this post uses.
6 high-leverage HubSpot → WhatsApp workflows
Workflow 1 - Lifecycle Stage = MQL → instant acknowledgement
Trigger: Workflow - Contact-based
Filter: Lifecycle stage = Marketing Qualified Lead
AND Phone number is known
Action: HubSpot workflow webhook → Zapier, Make, or n8n → Whatsable sends the template
To: {{contact.phone}}
Template: lead_acknowledgement
Variables: {{contact.firstname}}, {{contact.company}}
Note: Your Zapier, Make, or n8n scenario can write a note back to HubSpot if you want a trail on the contact.
Template body: “Hi {{1}}, thanks for the interest in {{2}} - got your details, we’ll respond inside the hour. Reply to this message if it’s urgent.”
The “reply to this message” line is deliberate. It opens the 24-hour conversation window so reps can free-text back from inside the native HubSpot inbox.
Workflow 2 - Deal Stage = Quote Sent → templated follow-up
Trigger: Workflow - Deal-based
Filter: Deal stage = Quote Sent
Action: HubSpot workflow webhook → Zapier, Make, or n8n → Whatsable sends the template
To: {{associated_contact.phone}}
Template: quote_followup
Variables: {{deal.dealname}}, {{owner.firstname}}
Single highest-leverage workflow in HubSpot if you sell anything that gets quoted. Replaces “I’ll follow up tomorrow” with “sent inside 30 seconds.”
Workflow 3 - Ticket status changed → status WhatsApp
Trigger: Workflow - Ticket-based
Filter: Ticket status changed (any of: In Progress, Waiting on Customer, Resolved)
Action: HubSpot workflow webhook → Zapier, Make, or n8n → Whatsable sends the template
To: {{ticket.requester_phone}}
Template: ticket_status_update
Variables: {{ticket.subject}}, {{ticket.status}}, {{ticket.url}}
The support automation everyone underestimates. We’ve seen this reduce inbound “any update?” tickets by roughly 30% in the teams that ship it (internal observation, your mileage will vary).
Workflow 4 - Renewal date - 30 days → outreach + CSM ping
Trigger: Workflow - Custom date-based
Filter: Renewal date = 30 days from today
Action 1: HubSpot workflow webhook → Zapier, Make, or n8n → Whatsable sends the template
To: {{contact.phone}}
Template: renewal_outreach
Variables: {{contact.firstname}}, {{deal.product_name}}
Action 2: Slack - Notify CSM channel with deal context
The two-step pattern is the most reliable accountability shape - customer hears something on the channel they actually read, CSM is internally on the hook to follow up.
Workflow 5 - Lead score crosses threshold → rep’s own WhatsApp
Trigger: Workflow - Contact-based
Filter: HubSpot score >= 75 (your threshold)
Action: HubSpot workflow webhook → Zapier, Make, or n8n → Whatsable sends the template
To: {{owner.phone}} ← the rep, not the customer
Template: rep_internal_alert
Variables: {{contact.firstname}}, {{contact.company}}, {{contact.hubspot_url}}
Most reps live in WhatsApp more than they live in HubSpot. This workflow meets them where they actually look.
Workflow 6 - Deal closed-won → thank-you + onboarding handoff
Trigger: Workflow — Deal-based
Filter: Deal stage = Closed Won
Action: HubSpot workflow webhook → Zapier, Make, or n8n → Whatsable sends the template
To: {{associated_contact.phone}}
Template: deal_won_thankyou
Variables: {{contact.firstname}}, {{owner.firstname}}
Template body: “{{1}} - really glad we’re working together. {{2}} will reach out tomorrow with onboarding details. Anything urgent before then, just reply here.”
Underrated workflow. Sets the tone for the relationship and opens the WhatsApp thread for onboarding without forcing a separate channel switch.
Three HubSpot-specific gotchas
1. Phone property discipline. HubSpot has multiple phone properties - phone, mobilephone, calculated variants, custom company phones. Pick one canonical field, standardise on +CountryCode, set the others to auto-populate from it. The Cloud API silently skips malformed numbers - your fire rate caps at around 70% if you skip this.
2. Approve templates before building workflows. Meta template review is 24-48 hours. If your template is still pending, your workflow will fire and fail silently. Submit Monday, ship Wednesday - and check the template status in the provider’s dashboard before going live.
3. Workflow re-enrollment trap. HubSpot’s “allow contacts to re-enroll” setting will fire the same WhatsApp multiple times when properties update in quick succession. For high-volume property-change workflows, either turn re-enrollment off, or filter on a specific value change (“property is exactly X”) rather than “property has any value.”
What you actually get
Once the 4-step setup is live and the workflows are wired:
- Property change in HubSpot fires a WhatsApp before the rep finishes typing the call summary
- Engagement logged on the contact record - the timeline shows WhatsApp next to email and call
- Customer replies land in the native HubSpot inbox - full two-way conversation
- Multi-number supported - route per team, per region, per business unit from one HubSpot setup
- Quality rating visible in the provider’s dashboard - yellow before red, with the signals that pushed you there
- Throughput scales with your number’s trust: 1K → 10K → 100K → unlimited messages per day
The shift in unglamorous terms: reps stop tabbing out to a separate app to send a follow-up. The contact timeline finally tells the truth about every channel the customer touched.
Where Whatsable fits
Whatsable is an official Meta Tech Provider - verified by Meta to provide WhatsApp Cloud API access. There is no Whatsable app in HubSpot. HubSpot fires a workflow webhook, Zapier, Make, or n8n catch it, and Whatsable sends the WhatsApp message.
You connect your number once through our console. We handle Meta Business Manager setup, business verification, template approvals, webhook retries, token rotation, and quality rating monitoring. You build the workflows, design the templates, ship the campaigns.
Start free at whatsable.app. Connect your number, fire a HubSpot webhook into Zapier, Make, or n8n, and send a real WhatsApp today. No credit card.
The point
HubSpot's native channel does inbound well. Outbound templates go out through a HubSpot webhook, Zapier, Make, or n8n, and Whatsable. Combined on one business number, you get both sides.
Most teams trying to wire HubSpot to WhatsApp either give up at the native channel (and miss the workflow side entirely) or default to unofficial WhatsApp Web automation (and lose the number to a ban within weeks). Neither is necessary.
Connect your number through an official Meta Tech Provider. Wire workflow 1 today.
Try Whatsable free at whatsable.app — no credit card required.