Integrate HubSpot with WhatsApp Business API — Ominiflow Guide

A HubSpot CRM WhatsApp integration closes the gap between your pipeline and the channel customers actually open. HubSpot WhatsApp automation is the deal-stage trigger: a deal moves to "Proposal Sent" and a WhatsApp template fires with the PDF link. A prospect replies on WhatsApp — the thread logs to their contact record before your rep even sees the notification. No copy-paste between tabs. No "did someone follow up?"

This guide walks through architecture, setup on Ominiflow, field mapping, outbound triggers, inbound logging, and the mistakes that break HubSpot syncs in production. For the underlying Cloud API model, start with our WhatsApp API integration guide.

Too long? Start here

• Flow: HubSpot event → Ominiflow → Meta Cloud API → customer; customer reply → Ominiflow webhook → HubSpot activity log
• Outbound business messages need approved templates unless the contact messaged you within the last 24 hours
• Setup: Connect WhatsApp on Ominiflow → Integrations → HubSpot → OAuth → map triggers and fields → test
• Phone numbers must be E.164 (+14155552671 or 919876543210 without spaces)
• Bi-directional sync covers deal stage changes, form submissions, lifecycle stage updates, and inbound chat logging
• Setup time: 30–60 minutes for basic triggers; 1–2 days for multi-pipeline routing with custom properties

Why integrate HubSpot with WhatsApp?

HubSpot holds your lead source, deal stage, owner, and lifecycle data. WhatsApp holds the conversation. Keeping them separate creates predictable failures:

• Lost context — reps reply on WhatsApp without seeing deal value or last email touch
• Delayed follow-up — form fills sit in HubSpot while the prospect expects a WhatsApp reply within minutes
• No attribution — marketing cannot tie broadcast replies back to campaign or deal source
• Manual logging — agents paste chat screenshots into notes instead of structured activity records

WhatsApp open rates routinely beat email for B2B and D2C in India, MENA, and LATAM. HubSpot's native WhatsApp features are limited compared to a dedicated BSP layer. Ominiflow sits between HubSpot and Meta — handling templates, inbox, webhooks, and compliance while HubSpot remains your system of record.

Integration architecture

Every production HubSpot + WhatsApp setup follows the five-layer pattern from our integration guide:

1. Source system (HubSpot) — fires events: new contact, deal stage change, form submission, ticket created, workflow enrollment
2. Integration layer (Ominiflow) — transforms HubSpot properties into WhatsApp-ready JSON; validates templates and phone format
3. BSP platform (Ominiflow) — routes to agents, runs chatbot flows, manages template library
4. Meta WhatsApp Cloud API — delivers message; handles encryption and delivery receipts
5. Inbound webhook — customer reply → Ominiflow → HubSpot timeline activity + optional deal/task update

Outbound pipe

HubSpot workflow or deal stage change → Ominiflow API → POST graph.facebook.com/v21.0/{phone_number_id}/messages → customer phone

Inbound pipe

Customer text → Meta webhook → Ominiflow → HubSpot contact match by phone → timeline note + owner notification

Heavy CRM writes should happen after acknowledging the webhook with HTTP 200. Queue them. Meta retries slow endpoints, and duplicate processing bites teams that are not idempotent.

The 24-hour rule (and why templates exist)

When a contact messages your business on WhatsApp, a 24-hour customer service window opens. Inside that window, agents can send free-form session messages from the Ominiflow inbox.

Outside the window — or for any business-initiated outreach triggered from HubSpot — you need a Meta-approved template. Match category to content: utility for order updates, marketing for promos, authentication for OTPs.

Setup steps

1. Connect WhatsApp on Ominiflow — complete Cloud API onboarding; number status CONNECTED. Guide: API setup
2. Navigate to Integrations → HubSpot in Ominiflow workspace settings
3. Authenticate via HubSpot OAuth — grant contacts, deals, timeline, and workflow scopes your use case needs
4. Map phone field — typically phone or mobilephone on contact; ensure E.164 format in HubSpot or normalize in Ominiflow
5. Configure outbound triggers — select HubSpot events (deal stage, lifecycle stage, workflow enrollment) and assign WhatsApp templates with variable mapping
6. Enable inbound logging — WhatsApp replies create HubSpot timeline activities on matched contacts
7. Test end-to-end — create test contact with your phone; trigger workflow; confirm delivery and CRM log

Field mapping reference

Use cases by team

Sales

• Speed-to-lead — HubSpot form submission → utility template within 60 seconds: "Hi {{1}}, thanks for your demo request"
• Deal stage automation — "Proposal Sent" → template with proposal link; "Closed Won" → onboarding sequence
• Stale deal nudge — HubSpot workflow on 7-day no-activity → marketing template (opt-in required)
• Owner handoff — reassigned deal → intro template from new rep via Ominiflow inbox

Marketing

• Lifecycle broadcasts — sync HubSpot lists to Ominiflow segments; run approved marketing templates
• Event follow-up — webinar attendance property → post-event template with recording link
• Click-to-WhatsApp ads — ad lead lands in HubSpot; welcome flow fires automatically

Customer success

• Renewal reminders — contract end date workflow → utility template 30/14/7 days before expiry
• Onboarding check-ins — day 3, 7, 14 post-close templates with help links
• CSAT collection — ticket resolved in HubSpot Service Hub → survey template on WhatsApp

Integration patterns

Native connector covers 80% of use cases. Reach for webhooks when you need custom JSON payloads or cross-system logic HubSpot workflows cannot express.

Common mistakes

• Wrong phone format — HubSpot stores local numbers without country code; normalize to E.164 before send
• Template variable mismatch — {{1}}/{{2}} order must match Meta-approved template exactly or delivery fails
• Marketing without opt-in — HubSpot list membership is not WhatsApp opt-in; collect explicit consent
• Duplicate triggers — deal stage workflow fires on every save, not just stage change; add enrollment filters
• No contact match on inbound — phone normalization mismatch means replies do not log; standardize format both ways
• Sending promos as utility templates — Meta rejects or restricts; use correct category

Prerequisites

Before installing the Ominiflow WhatsApp integration, ensure you have the following:

• Ominiflow Account: An active account on app.ominiflow.com with an active plan.
• HubSpot Account: A HubSpot account with Super Admin or App Marketplace installation permissions.
• WhatsApp Business API: An active WhatsApp Business number connected via Meta Cloud API on Ominiflow.

Installation & Setup Steps

1. Install the App: From the HubSpot App Marketplace, search for Ominiflow - WhatsApp Automation and click Install App (or go to your Ominiflow dashboard > Integrations > HubSpot).
2. Authorize Connection (OAuth 2.0): You will be redirected to the secure HubSpot authorization screen. Select your HubSpot account and approve the requested permissions (contacts, deals, and timeline).
3. Configure Event Triggers: In your Ominiflow HubSpot Settings, review the Automated WhatsApp Triggers table. Assign approved WhatsApp templates to HubSpot events like Contact Creation, Form Submissions, and Deal Stage movements.
4. Map Variables: Match HubSpot contact and deal properties (e.g. firstname, dealname, phone) with template placeholder variables ({{1}}, {{2}}).
5. Verify Connection: Once connected, the status badge will display Connected and your HubSpot integration is immediately active.

How to Use the Integration

Once installed, you can use Ominiflow directly inside HubSpot:

• CRM App Card: Open any Contact or Deal record in HubSpot CRM. Look at the right sidebar for the Ominiflow WhatsApp card. You can view WhatsApp status and click "Open in Ominiflow" to immediately message the customer or view chat history.
• HubSpot Workflows: In HubSpot Workflow builder, add the action "Send WhatsApp Message via Ominiflow" to trigger automated notifications whenever criteria are met.
• Timeline Activity: Inbound and outbound WhatsApp messages are automatically logged to the contact's HubSpot CRM timeline for full visibility across your sales and support teams.

How to Disconnect the App

If you need to disconnect HubSpot from Ominiflow:

1. Log in to your Ominiflow Workspace.
2. Navigate to Integrations > HubSpot Settings.
3. Under the HubSpot Connection box, click the red Disconnect HubSpot button.
4. Confirm the disconnection prompt.

Note: Disconnecting stops future automated triggers and chat logging. All historical contacts, deals, and timeline activity previously synced will remain safely preserved in your HubSpot portal.

How to Uninstall the App

To completely remove Ominiflow from your HubSpot portal:

1. In your HubSpot account, click the Settings icon in the top navigation bar.
2. In the left sidebar menu, go to Integrations > Connected Apps.
3. Find Ominiflow - WhatsApp Automation, click the Actions dropdown, and select Uninstall.

For more details, refer to the official HubSpot Knowledge Base article on uninstalling apps.

Troubleshooting

Integrate on Ominiflow

Ominiflow ships native HubSpot OAuth integration with deal-stage triggers, contact timeline logging, template management, and shared team inbox. Pair with Slack alerts for real-time lead notifications.

Set Up HubSpot Integration →

Related: All integrations · API integration guide · Zoho CRM integration

FAQ