Match it to what the Workflow enrolls. Contacts take the (Contact) version; anything else takes (Object). In a contact-enrolled Workflow you will see both — the Contact one is the version that cannot be mis-typed, because it never asks you for a record ID.
Voxie for HubSpot Updated September 2026 Text your customers straight from a HubSpot Workflow
The Voxie app adds SMS to HubSpot Workflows. Send a message the moment a record reaches the step, or push contacts into Voxie as an audience and campaign to them there. Both paths report into the same analytics.
New in September 2026. You can now send an SMS directly from a Workflow, Workflows enrolled on any HubSpot object can use every Voxie action, and the actions have been renamed into (Contact) and (Object) pairs. If you have Workflows built on the earlier action names, open each one and confirm the Voxie step is still configured the way you expect.
Send a message
Write the text in the Workflow and Voxie sends it when the record arrives. No campaign to build on the Voxie side.
How to set it upBuild an audience
Push records into Voxie as an External List and use it in a Quick Blast or an Evergreen Campaign, with full personalization.
How to set it upWork from any object
Deals, companies, tickets and custom objects can all drive Voxie actions — not only Workflows enrolled on contacts.
How to set it up
The app
The Voxie actions
The app adds eight actions to the HubSpot action picker. Each comes in two versions. Which you pick depends on what your Workflow is enrolled on, not on what you want to do.
| Action | Use when the Workflow enrolls... |
|---|---|
| Send SMS (Contact) | Contacts |
| Send SMS (Object) | Deals, companies, tickets, custom objects |
| Add to New List (Contact) | Contacts |
| Add to New List (Object) | Deals, companies, tickets, custom objects |
| Add to Existing List (Contact) | Contacts |
| Add to Existing List (Object) | Deals, companies, tickets, custom objects |
| Remove from List (Contact) | Contacts |
| Remove from List (Object) | Deals, companies, tickets, custom objects |
The difference that matters
The (Contact) version fills in the identifying fields for you — record ID, email, first name and last name all come from the contact. The (Object) version cannot assume those exist on the record, so it asks you to map each one.
That is the whole reason there are two of each. The Object version can technically target a contact as well, but it would still ask for every mapping — so a contact-enrolled Workflow gets a shorter, safer form of its own.
Rule of thumb: if the Workflow enrolls contacts, use the (Contact) action. It is the version that cannot be mis-typed, because it never asks you for a record ID.
Renamed from earlier versions. “Add to new Voxie contact list” is now Add to New List (Contact), “Add to existing Voxie contact list” is now Add to Existing List (Contact), and “Remove from Voxie contact list” is now Remove from List (Contact).
Every action
Target record
Every Voxie action starts with Target record, which decides whose details the action uses. The default is the record the Workflow enrolled. You can also follow an association and act on a related record — so a Workflow enrolled on one object can message a contact associated with it, without needing a separate Workflow for that object.
When the Workflow enrolls contacts and you want to message that contact, leave Target record on the enrolled contact. Following an association when you do not need one is the easiest way to message the wrong person.
Path 1
Send an SMS from a Workflow
Use this when the Workflow already knows the timing — an appointment reminder, a post-visit follow-up, an anniversary message. Keep using External Lists when you want Voxie to own the audience and the send.
Add the action
- Open your Workflow and click + where the message should go.
- Choose Voxie, then Send SMS (Contact) or Send SMS (Object).
- Fill in the fields below.
- Click Save, then turn the Workflow on.
The fields
Use this when your Workflow is triggered by contacts. Voxie reads the record ID, email and name from the contact, so it never asks you for them.
| Field | Required | What you supply |
|---|---|---|
| Target record | Yes | Leave it on Enrolled contact. |
| Campaign name | Yes | How this send is labelled in Voxie reporting, for example “Voxie: Anniversary text”. |
| Message | Yes | Your copy, held to the same brand standards as a Voxie campaign. Add HubSpot personalization tokens here. |
| Phone number | Yes | Select the contact’s mobile phone property. Every account stores this differently. |
| Group ID | No | A location’s Group ID sends from that location’s number. Blank sends from corporate. |
| Audience type | Yes | Pick the type that matches the message. |
Send SMS field
Audience type
Every Send SMS action declares what kind of message it is. Voxie uses this to decide whether a given contact is allowed to receive it. Pick one to see what it means.
Marketing
Promotions, offers and announcements — anything you are sending because you want to, rather than because the guest did something.
A contact who is not already subscribed in Voxie will not receive these. The message is skipped, not queued, and the Workflow raises no error — so HubSpot’s enrolled count and Voxie’s sent count will differ.
Send SMS field
Which number it sends from
Set by Group ID, and the field most worth getting right. Choose what you would put in it:
Sends from that location’s number
The guest sees a local number and replies land with that location. This is what you want for anything a location would follow up on.
Timing and quiet hours
Voxie sends the message as soon as a contact reaches the step. There are no timing controls on the action, and the safe sending hours you set on Voxie campaigns do not carry over to HubSpot.
Sending outside permitted hours is a compliance matter in most jurisdictions. Because Voxie sends on arrival, a Delay step is what keeps a Workflow compliant — it is not optional in practice.
Repeat sends are controlled by the HubSpot Workflow’s re-enrollment settings, not by Voxie.
Add a Delay before the Send SMS step
To keep texts from landing too early or too late, put a HubSpot Delay immediately before the Voxie action.
- Add a Delay step above Send SMS.
- Set Delay to Until a specific time of day.
- Pick the time you want the text to land.
- Choose Use contact time zone, not the account time zone.
Contact time zone is the part people miss. Without it, a guest three time zones away gets the text three hours off.
Writing the message
The message body takes HubSpot personalization tokens. It does not take Voxie merge fields or Liquid — a Send SMS action skips Voxie’s message templating.
A property that is empty sends as empty. There is no fallback. “Welcome to {{ location }}” reaches a contact with no location as “Welcome to ”. Require the properties your message depends on in the enrollment trigger so a record with gaps never reaches the step.
Hold the copy to the same brand standards as a Voxie campaign.
There is no emoji picker on the action. Paste an emoji in, or use your operating system’s emoji shortcut.
Voxie adjusts the text before sending where it saves you money. A curly apostrophe or an em dash, with no emoji present, is replaced with its plain equivalent so the message sends as one segment type rather than another — which can halve the segment count. Add an emoji and Voxie sends the message exactly as written.
Before you turn the Workflow on
Testing
HubSpot’s Workflow test shows the path a record takes but does not run the Voxie action, so no message is sent. To test a real send, copy the Workflow, set the copy to manual enrollment, turn it on, and enroll yourself.
Backfill
When you turn a Workflow on, HubSpot offers to enroll every record that would have met the trigger in the past. On a Send SMS Workflow that means texting all of them at once. Choose to enroll going forward only, unless you have deliberately decided otherwise and checked the number.
Path 2
Build an audience in Voxie
The list actions push records into Voxie as an External List, ready to use in a Quick Blast or an Evergreen Campaign. Use this path when you want Voxie to own the audience, the schedule and the message.
How it works
- Records that meet Voxie’s requirements are taken from the Workflow.
- They are pushed to Voxie as an External List.
- Selected HubSpot properties are mapped to Voxie contact and custom attributes.
- The list becomes available as a campaign audience, with full personalization.
You can use more than one Voxie action per Workflow, each building a different list. List names sync back from Voxie, so Add to Existing List and Remove from List let you pick from a menu rather than retyping a name.
Field mapping
| Field | Required | Notes |
|---|---|---|
| External List name | Yes | How the list appears in Voxie. |
| Phone number | Yes | The primary identifier in Voxie. |
| Email, record ID | Yes | Used for identification and sync. |
| First, last name | No | Identification and personalization. |
| Contact time zone | No | Lets Voxie campaigns send at local times. |
| Preferred group | No | Maps the contact to a location. |
| Properties | No | Up to 10, mapped as custom attributes. |
| Tags | No | Up to two, mapped as Voxie tags. |
Analytics
Reporting
Messages sent from a Workflow
Each Send SMS action creates an External Campaign in Voxie, named with the Campaign name you entered. Four actions means four campaigns, each reporting its own sends, click-through rate and replies.
Finding them in Analytics
- Go to Analytics → Outbound Messages.
- In the Filters panel, under Resource Type, tick External Campaign. Untick the rest to see HubSpot-sent messages on their own.
- Narrow further with Range, Sender Type and Audience Type — so you can look at, say, only Transactional messages from one location.
Each campaign appears under the Campaign name you typed into the action, which is why that field is worth naming properly.
An External Campaign does not appear in the Campaigns list. The content and audience live in HubSpot; Voxie sends the message and reports on it.
What you can measure
A message sent from a HubSpot Workflow is measured exactly like one sent from Voxie. The same reporting a Quick Blast or an Evergreen Campaign gets.
- Volume
- Messages Sent · SMS Messages Sent · MMS Messages Sent · Contacts Messaged
- Performance
- Message Deliverability · Unique Click-Through Rate · Click-Through Rate · Message Reply Rate
- Health
- Unsubscribe Rate
- Over time
- Messages Sent by Day, split by audience type
- Per campaign
- Messages Sent, Unique Click-Through Rate, Message Replies and Unsubscribes per Resource, each ranked
Setup
Install the app
Connect
- Contact your Voxie team to activate the HubSpot integration on your account.
- Sign in to Voxie and open Settings.
- Go to HubSpot under Integrations.
- Click Connect HubSpot account.
- Choose the HubSpot account to grant access to.
Voxie admin access is required to manage integrations. Access to the Voxie app in HubSpot requires a signed agreement.
Disconnect
In Voxie, go to Settings → Integrations → HubSpot and click Disconnect HubSpot Account.
After disconnecting, Workflows can no longer send contact information or messages through Voxie. Existing data stays on your HubSpot records.
To remove the app from HubSpot entirely, follow HubSpot’s own instructions for uninstalling an app.
Common questions
Voxie applies subscription status at send time. A Marketing message is not sent to a contact who is not opted in to marketing — it is skipped, not queued, and the Workflow raises no error. HubSpot counts who entered the Workflow; Voxie counts who was allowed to be messaged.
Not on the action itself. Add a HubSpot Delay step before it, set to Until a specific time of day with Use contact time zone selected.
No. Use HubSpot personalization tokens. Voxie templating is not applied to a Send SMS action, so Liquid and Voxie attributes pass through as literal text.
It sends as an empty space, with no fallback. Require the properties your message depends on in the enrollment trigger so a record with gaps never reaches the step.
In Voxie's outbound message analytics, under the Campaign name you gave the action. Each action creates its own External Campaign. They do not appear in the Campaigns list.
The phone number. If two HubSpot records share one number they resolve to the same Voxie contact, and the most recent values win.
Yes, and they are controlled by the HubSpot Workflow's re-enrollment settings rather than anything in Voxie.