Skip to content

Capture WhatsApp opt-in and log verifiable consent before any template is sent

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact11 stepsUpdated for HubSpot seat pricing
OutcomeEvery contact who agrees to WhatsApp messages carries a dated, sourced consent record and a usable WhatsApp number, and one gate property tells every other WhatsApp workflow whether it may send.
Workflow mapmessaging-004
Form submitted with WhatsApp box ticked leads to Stamp consent date and source and wording. Stamp consent date and source and wording leads to Subscribe to WhatsApp subscription type if used. Subscribe to WhatsApp subscription type if used leads to WhatsApp Phone Number known. WhatsApp Phone Number known leads to Yes: Set WhatsApp ready; No: Mobile Phone Number known. Mobile Phone Number known leads to Yes: Copy mobile to WhatsApp Phone Number and set ready; No: Set consent no number and create task. Yes No Yes No Form submitted with WhatsApp box ticked Stamp consent date and source and wording Subscribe to WhatsApp subscription type if used WhatsApp Phone Number known Set WhatsApp ready Mobile Phone Number known Copy mobile to WhatsApp Phone Number and set ready Set consent no number and create task
Form submitted with WhatsApp box ticked leads to Stamp consent date and source and wording. Stamp consent date and source and wording leads to Subscribe to WhatsApp subscription type if used. Subscribe to WhatsApp subscription type if used leads to WhatsApp Phone Number known. WhatsApp Phone Number known leads to Yes: Set WhatsApp ready; No: Mobile Phone Number known. Mobile Phone Number known leads to Yes: Copy mobile to WhatsApp Phone Number and set ready; No: Set consent no number and create task. Yes No Yes No Form submitted with WhatsApp box ticked Stamp consent date and source and wording Subscribe to WhatsApp subscription type if used WhatsApp Phone Number known Set WhatsApp ready Mobile Phone Number known Copy mobile to WhatsApp Phone Number and set ready Set consent no number and create task

When to use it, when not to

Use it

  • Use it before you build any workflow with the Send WhatsApp message action. The action needs verifiable opt-in consent, and this fiche is where that proof is created.
  • Use it when WhatsApp consent comes from a form checkbox, a landing page or an import of documented opt-ins.
Read more on when to use itShow less

Skip it

The rest of this spec

Prerequisites · 9 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 11 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 6

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 5 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free SMS and WhatsApp spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library