HubSpot SMS Integration With Consent Sync
A HubSpot SMS integration lets you text contacts from your CRM data and log every message back to the contact record. ColdTexting syncs contacts, consent status and replies as HubSpot activities, enrolls contacts in sequences from workflows and also connects to Pipedrive, Zapier and Salesforce.
Field mapping
Your CRM stays the source of truth for every contact
Reps keep working in HubSpot. Texts, replies and opt-outs show up there without anyone copying a thing.
A HubSpot SMS integration connects your CRM to a texting platform so contacts flow in, messages flow back and both systems agree on who may be texted. In ColdTexting the connection is a field map: you choose which HubSpot property holds the mobile number, which one holds SMS consent and which lists sync. Consent changes travel both ways, so a STOP reply updates HubSpot within the same sync.
Supported CRMs
What each integration covers and which plan includes it
Every connector carries the same core data, because consent and opt-outs are useless if only half of your systems know about them.
| Synced data | HubSpot | Pipedrive | Salesforce | Zapier |
|---|---|---|---|---|
| Contacts and mobile numbers | Yes | Yes | Yes | Yes |
| Consent status and source | Yes | Yes | Yes | Yes |
| Sent texts and replies as activities | Yes | Yes | Yes | As Zap actions |
| STOP written back to the contact | Yes | Yes | Yes | As a Zap trigger |
| Start a sequence from the CRM | From workflows | Through Zapier | Through webhooks or API | From any Zap |
| Included from plan | Growth | Growth | Scale | Growth |
Pipedrive SMS and Salesforce SMS integration work the same way as HubSpot. Scale also opens webhooks and the REST API for in-house systems, so a custom CRM can read the same consent records and reply events.
Send SMS from HubSpot
Texting starts in a workflow and ends on the timeline
Most teams never open a separate screen to start texting. A HubSpot workflow checks consent and enrolls the contact in SMS sequences, the steps send inside quiet hours, and each message and reply lands on the contact timeline as an activity. When the lead answers, the sequence stops and the thread goes to the contact owner set in HubSpot.
Setup
Connected in an afternoon without a developer
The integration lives in settings. An admin with CRM access finishes it in four steps.
Sales teams that text from the CRM tend to follow the playbook on texting for sales teams. Plan limits for each connector are listed on the page of plans with CRM sync.
- 01 Connect the accountSign in to HubSpot, Pipedrive or Salesforce from ColdTexting settings and approve access for your portal.
- 02 Map the fieldsPoint ColdTexting at the properties that hold the mobile number, owner and SMS consent. Create a consent property if you do not have one.
- 03 Choose the listsPick which lists or views sync. Contacts without a consent value import as held, not as sendable.
- 04 Test with one recordText your own contact, reply STOP and watch the consent property change in the CRM.
FAQ
Questions about CRM SMS integrations
Yes. Contacts sync from HubSpot to ColdTexting, sequences start from HubSpot workflows and every sent message and reply appears on the HubSpot contact timeline.
Yes. A STOP reply updates the consent status in ColdTexting at once and syncs back to the CRM contact.
HubSpot, Pipedrive and Zapier on Growth and higher, and Salesforce plus webhooks and a REST API on Scale and Enterprise.
No. You connect the CRM account from settings, map fields and choose which lists sync.
Related pages
Connect your CRM and keep consent in step
HubSpot, Pipedrive and Zapier sync come with Growth from $74 per month billed yearly. Salesforce, webhooks and the REST API come with Scale.