HubSpot is a genuinely good trigger source: workflows can fire on almost any property change, and a webhook action means you do not need custom code to reach your messaging provider. The care required is all on the consent side.
The mechanics
- A workflow triggered on the property change you care about — lifecycle stage, deal stage, a form submission, a meeting booked.
- A webhook action posting to your own endpoint, not directly to the provider. The indirection is what lets you enforce suppression and pacing.
- Your service checks consent and quiet hours, then sends.
- Inbound replies written back as a HubSpot engagement, so the timeline is complete.
Never point the workflow straight at your provider
It is tempting — one webhook action and you are sending. But then nothing checks whether the contact opted out, whether it is 2am where they live, or whether you already messaged them twice today. Put your own service in the middle. It is thirty lines and it is the difference between a programme and a liability.
Consent in HubSpot specifically
HubSpot has subscription types and legal basis fields, and they are built around email. You need an SMS/messaging-specific consent property with a source and a timestamp, and your send path must read it. Do not reuse the email subscription status — someone who wants your newsletter has not agreed to be texted.
| Property | Why |
|---|---|
messaging_consent | Boolean. The thing you check at send time. |
messaging_consent_source | Where it came from — form name, phone call, in person. |
messaging_consent_date | When. This is what you produce if anyone asks. |
phone_e164 | Normalised number. Stops the same person getting two messages. |
B2B has a legal wrinkle
Most HubSpot portals are B2B, and there is a widespread assumption that business-to-business messaging is exempt from consent rules. In the US it is not — TCPA governs messages to mobile numbers regardless of whether the recipient is at work. A contact who filled in a form is a different proposition from a purchased list. The B2B playbook and its constraints.
What to trigger on
- Meeting booked — confirmation, then a reminder from your own scheduled job.
- Form submission on a high-intent page — a fast, human, one-question message. This is the speed-to-lead play and it is the strongest use of this channel. Why speed is most of the effect.
- Deal stage change — only where the customer would expect to hear from you. A stage change is your internal state, not news.
- Renewal date approaching — with the value summarised, not just the date.
Before enabling the workflow
- Messaging consent property exists, populated, and read at send time.
- Your own service sits between HubSpot and the provider.
- Quiet hours enforced in the contact's timezone.
- A per-contact frequency cap, so overlapping workflows cannot pile on.
- Replies written back to the contact timeline.
- Opt-out sets the consent property to false, immediately.