Send iMessage from HubSpot workflows — and the mistakes that break it
A HubSpot-specific walkthrough that spends as much time on the failure modes as on the setup. Connect the portal, add Send iMessage to a workflow, then go through the four things that make a message silently not arrive — and where in HubSpot and Tuco you look to see which one it was.
What you will be able to do
- Connect HubSpot from Integrations → CRM and confirm scopes
- Add Send iMessage to a HubSpot workflow and map the phone property
- Keep phone numbers in E.164 so the send is accepted
- Understand why a missing first name stops the whole message
- Add the Tuco card to the contact record for two-way replies
Chapters
Timestamps open YouTube at that moment. 15 sections across 10:25.
- 0:00
What this covers
The native HubSpot integration, plus the quirks that keep a line healthy.
- 0:23
Connect HubSpot
Integrations → CRM → Connect HubSpot, choose the portal, approve, then test scopes and watch contacts flow in.
- 1:41
Build the workflow
Automation → Workflows → Create from scratch, at contact level.
- 2:06
What this is for
Form fills, ads, speed to lead. Not bulk texting — bulk texting over iMessage is what gets a line banned.
- 2:35
Add Send iMessage
The Tuco action block appears in the workflow action list once the integration is connected.
- 2:47
E.164 phone numbers only
Ten digits with no country code will not send. Check how the property is actually stored in your CRM.
- 3:29
The missing-first-name trap
If you reference a first name in the copy and the contact has none, the message does not go out at all.
- 3:38
Attachment URL — follow-ups only
Voice notes and images are fine from message two onward. The first message has to be plain text with no links.
- 4:16
Uploading audio
Leads → Upload Audio, or any publicly loadable URL. Open it in incognito to confirm; YouTube and Vimeo links do not work.
- 4:54
Line selection
Pin a line when you are routing by sales rep. Leave it blank if the workspace has one line. Do not paste a phone number here.
- 6:20
Duplicate detection while testing
Sending the same message to the same contact twice gets deduplicated. Activity logs show what was dropped.
- 7:26
Enrollment history
HubSpot enrollment history shows every step a contact took, which is where you confirm the action actually succeeded.
- 7:51
The daily limit
50 new contacts per phone per day. Over that, messages are rescheduled rather than sent, to protect the line.
- 8:18
Two-way sync on the record
Customize the contact view, add the Tuco card from the card library, and reply straight from the record.
- 9:52
The mistakes, restated
Valid E.164 number, no links or attachments in the first text, no duplicate sends, and do not exceed 50 a day on one line.
