How to Send WhatsApp Messages in HubSpot Workflows Without Breaking the Spam Act

WhatsApp isn't a fringe channel anymore, it's where business conversations actually happen. Prospects reply to WhatsApp in minutes. They ignore email for days.

So it makes sense that HubSpot users want sequences that mix both channels: send a message here, follow up there, stop automatically when the prospect replies on either channel. Most people start in the wrong place, hit a wall immediately, and assume HubSpot can't do it.

It can. You just need Workflows, not Sequences.

Why Sequences won't work here

HubSpot Sequences only support four step types: email, call task, LinkedIn task, and general task. There's no WhatsApp step and no way to add one.

Contact-based Workflows are where this lives. They let you combine Send email and Send WhatsApp message actions with delays in between, exactly the multi-channel sequence you're trying to build. More involved to set up, but fully capable.

What you need first

Before touching a single workflow, three things need to be in place.

1. Marketing Hub or Service Hub Professional or Enterprise. WhatsApp is native at these tiers. On Starter or Free, you'll need a third-party tool like Wati, Rasayel, or Respond.io instead.

2. A connected WhatsApp Business account. HubSpot connects to WhatsApp via Meta's WhatsApp Business Platform, this is the business API, not the regular WhatsApp or WhatsApp Business app. You need a verified WhatsApp Business account connected to your HubSpot inbox under Settings > Inbox > Inboxes > Connect a channel > WhatsApp.

3. Approved, automation-ready message templates. WhatsApp blocks free-form outbound messages, so every message your business initiates needs a pre-approved template. When publishing in HubSpot, choose Publish for automation (not Publish for CRM) so workflows can use it. Meta approval takes a few hours to a few days.

Consent first, everything else second

This section isn't optional reading. HubSpot enforces WhatsApp opt-in at the platform level: if a contact doesn't have an active WhatsApp subscription on their record, the workflow step fails silently. No message, no obvious error.

What counts as valid consent:

• Meta requires verifiable opt-in before any business-initiated message. As of its November 2024 update, general consent naming WhatsApp as a channel is technically sufficient under Meta's rules.
• GDPR goes further for EU and UK contacts. Consent must be specific to WhatsApp as a processing activity, a general SMS opt-in isn't enough, even if Meta accepts it.
• Australia goes further again, in a different direction. Under the Spam Act 2003, you need either express consent, the person knows and accepts they'll get WhatsApp messages from you, or inferred consent, where they gave you the number directly and would reasonably expect a message like this given an existing relationship. Meeting Meta's November 2024 bar does not automatically meet this one. They are separate tests, and the ACMA is clear that the burden of proving consent sits with the business that sent the message, not with Meta or with HubSpot.

The safe standard: explicit, channel-specific, and informed. The contact knows they're opting in to WhatsApp messages from your business, what kind, and how to opt out. Don't rely on pre-checked boxes or recycled SMS consent.

How to collect and track it in HubSpot:

1. Add a WhatsApp consent checkbox to your forms with clear language ("I agree to receive WhatsApp messages from [Business] about [topic]") and map it to the contact's WhatsApp subscription status.
2. In your workflow, make Manage communication subscriptions the first action, before any WhatsApp send. This records consent on the record before the message fires.
3. Make sure every template identifies your business by its correct legal name, or name and ABN, since that's a separate Spam Act requirement and it applies even when a template is sent under a staff member's name.

Why it matters: without valid opt-in, Meta can reject templates, block messages, or suspend your number, and a suspended number takes down every team using it, not just your workflow. That's Meta's enforcement. The Spam Act sits on top of it and is yours to answer for separately: if the ACMA ever asks you to prove consent, "Meta approved the template" is not the same answer as "here is the record of when and how this person opted in".

How to build it

Step 1: Plan the sequence

Map it before you build it. A typical multi-channel cadence:

• Day 0: Email (intro or value proposition)
• Day 2: WhatsApp (short, conversational follow-up referencing the email)
• Day 5: Email (case study, resource, or direct ask)
• Day 7: WhatsApp (final low-pressure touch)

Keep WhatsApp messages short and personal. Meta reviews templates for quality and rejects anything that reads like a formatted marketing blast.

Step 2: Build the workflow

Go to Automation > Workflows and create a Contact-based workflow from scratch.

1. Set the enrolment trigger: a lifecycle stage, form submission, or list membership. For manual control, trigger off a static list and add contacts deliberately.
2. Check re-enrolment in the Settings tab. For outreach sequences, keep it off so contacts don't loop through twice.
3. Build the actions:
   • Manage communication subscriptions, set WhatsApp to subscribed (your consent step).
   • Send WhatsApp message: select your number, automation-published template, and personalisation tokens.
   • Delay: set your gap (for example, 2 business days).
   • Send email: choose a template or build inline.
   • Continue alternating sends and delays.

Step 3: Handle the "pause on reply" problem

This is the honest limitation. Understand it before you go live.

• Email replies, nearly native. In the Settings tab, add an unenrolment trigger on "Marketing email replied is greater than 0." The catch: contacts inside a delay are not unenrolled until they reach the next action. Reply on day 3 of a 5-day delay, and they stay enrolled until day 5.
• WhatsApp replies, no native option. There's no workflow trigger for inbound WhatsApp messages. To pause on a WhatsApp reply, a third-party tool catches the inbound message and updates a custom contact property, which your workflow then uses as an unenrolment trigger. It works, but it adds complexity that needs careful testing.

Two things that will catch you out

• The 1,000-message cap. HubSpot limits outbound template messages to 1,000 per month across all connected WhatsApp accounts, resetting on your subscription anniversary. At any real volume, this matters fast. Third-party tools run on separate limits, which is why high-volume teams often skip native HubSpot.
• WhatsApp Coexistence (new, but check availability). HubSpot now supports Coexistence, letting your team use the WhatsApp Business app and the HubSpot inbox on the same number at once, with real-time sync across mobile, web, and desktop and a 180-day conversation backfill. Useful if you want reps replying from their phones while HubSpot still logs everything. Two caveats: it doesn't solve the workflow reply-detection problem above, and Meta's Coexistence rollout excludes several regions, so confirm it's available for your number before relying on it.

When to use a third-party tool instead

Native HubSpot setup works well for:

• Under 1,000 messages per month
• Sequences where email reply detection is enough
• Straightforward two or three-step cadences

Reach for a dedicated platform (Wati, Rasayel, Respond.io) when you need inbound WhatsApp reply detection, higher volume, conversational branching, or heavier template management. These are built for WhatsApp at this kind of volume and handle reply detection natively.

Want to build this properly?

The setup above is doable for an intermediate admin. The reply-detection piece, getting it to work reliably on WhatsApp, is where most teams get stuck, and getting it wrong costs real conversations with real prospects.

If you want the full sequence built right, consent tracked and provable under Australian law as well as Meta's, and the integration sorted so it actually pauses on a WhatsApp reply, that's the kind of implementation our RevOps and HubSpot team does at Neighbourhood.

We're a Diamond HubSpot Partner. Get in touch and we'll put the right setup in place the first time.

Talk to us about your HubSpot setup.

Get more hacks like this

Ops Intel is our newsletter for HubSpot admins and RevOps teams, practical, no-filler hacks and updates straight to your inbox every week. Subscribe to Ops Intel.

We're also on Facebook and YouTube with visual walkthroughs of setups like this one. Come find us there.