Twilio + HubSpot SMS integration: the complete 2026 guide

Twilio is where a lot of businesses already send their text messages from. HubSpot is where the customer record lives. Getting the two to talk to each other is one of the most-searched HubSpot integration questions, and one of the most poorly answered — most of what ranks is either a developer tutorial that skips the compliance half, or a landing page that skips the price.

This is the whole picture: what HubSpot does and doesn't do on its own, what an integration has to handle, which plan you need, what it costs per month once everything is running, and how to evaluate the options.

Does HubSpot integrate with Twilio out of the box?

No. There is no official Twilio-built app in the HubSpot App Marketplace, and no Twilio connection in HubSpot's settings.

This confuses people, because HubSpot does sell its own SMS product as a Marketing Hub add-on. That's a separate arrangement with its own phone numbers and its own bill — it isn't a way to use the Twilio account you already have. If you have Twilio numbers, Twilio credit, and Twilio's rates, none of that carries across.

So connecting Twilio to HubSpot means one of three things: a third-party app from the marketplace, a custom integration you build, or an automation tool like Zapier stitching the two together. We compared those routes in detail.

What a real integration has to do

It's worth being precise about this, because "sends a text" is about a fifth of the job. Five things have to work before texting from HubSpot feels like part of HubSpot rather than a bolt-on:

1. Send from a workflow. An action in the workflow editor, next to "send email" and "create task", so automated reminders and follow-ups can go out without anyone clicking anything.

2. Send from a contact record. A rep looking at a person's record needs to text them without opening another tab, copying a number, and losing the thread.

3. Receive replies. Someone will text back within a minute of your message arriving. If nothing in HubSpot is listening, your reminder system is a broadcast tower — and customers who reply and hear nothing back stop replying.

4. Match the message to the right contact. An incoming text is just a phone number and some words. Something has to search the CRM for whoever owns that number — and have an answer for when nobody does, rather than dropping the message on the floor.

5. Log everything, with delivery status. Both directions, on the contact's timeline, with Twilio's real delivery result. "Sent" is not "delivered" — a message the carrier rejected shows as sent everywhere except the place that bothers to ask.

Most integrations do one, two, or three of these. When you're evaluating options, work down this list rather than reading the feature grid.

Which HubSpot plan you need

The gates here are HubSpot's, and they trip people up more than anything else about texting.

The row that decides most purchases is the third one. If you're on Sales Hub Professional and you try to build this yourself with a webhook action, you'll discover partway through that the webhook action isn't included and you need Operations Hub as well. An app's workflow action doesn't have that requirement — it's a normal app action, so any hub with workflows can use it.

What it actually costs per month

Here's the arithmetic nobody puts in the marketing copy. Assume a small team in the US: one local phone number, 2,000 outbound messages a month, and 400 replies.

So Twilio carriage for a genuinely useful volume of texting is roughly $25 a month. That's the number to hold onto, because it reframes everything else: if an integration charges per message on top, you're paying a markup on the cheap part. Pricing that scales with your message volume, rather than with what the software does, is the thing to look at hardest.

Two more cost traps worth naming:

• Message segments, not messages. A text over 160 characters is split and billed per segment. One emoji switches the whole message to a different encoding and drops the limit to 70 characters — so an emoji in a 150-character message can double its cost.
• Per-channel pricing. Some apps charge per phone number or per "channel". Fine with one number. Expensive the moment sales and support want separate numbers.

Twilio's rates move, and vary by country. Treat these as the shape of the bill, not a quote.

A2P 10DLC: the part that decides whether any of this works

If you're texting US numbers, your phone number has to be registered with the carriers before it will deliver anything. This is A2P 10DLC, and since early 2025 the major US carriers block unregistered traffic outright rather than filtering it.

What makes it dangerous is that nothing tells you. Twilio accepts the message. Your integration reports success. The recipient gets nothing. Teams lose weeks to this before someone thinks to check registration.

The process: register your business as a brand, register a campaign describing what you'll send, attach your number. Fifteen minutes of forms, brand approval within hours, campaign approval in roughly ten to fifteen days. Start it the day you decide to do this, not the day you're ready to send.

We wrote a full walkthrough for HubSpot admins, because Twilio's own documentation is written for developers.

Toll-free numbers take a different route — Toll-Free Verification — with much the same effort. Unverified toll-free traffic is blocked too.

Choosing between the marketplace apps

Search "twilio" in the HubSpot App Marketplace and you'll find a handful of options, with review scores that are, charitably, mixed. The complaints cluster in the same few places, so those are the places to check:

Does it have a workflow action? Several are inbox-only. If you came for automation, confirm it exists rather than inferring it from the word "workflows" appearing somewhere on the listing.

How does it price? Flat, per number, per user, or per message credit. Credit systems are the most common source of complaints — people run out mid-campaign and can't tell what a credit is worth.

How long does setup actually take? Reviews are the honest source here. A Twilio integration should be a matter of minutes: paste an API key, pick a number. If reviewers describe waiting weeks for numbers to be provisioned, that's a company reselling you numbers rather than connecting the ones you have.

Does it ask for your Auth Token? It shouldn't. Twilio API keys exist so that a third party can be given revocable access without holding the master credential to your account. An integration asking for your Auth Token is telling you something about how carefully it was built.

What happens on failure? The difference between "message failed" and "the carrier rejected this because the number isn't A2P registered — here's how to fix it" is the difference between a five-minute fix and a support ticket.

Which plan does it require of you? Some features are gated by HubSpot, as the table above shows. A good listing says so plainly. A listing that doesn't is setting up its own bad reviews.

Setting it up

With an app, the sequence is short:

1. Install the app from the marketplace and approve the permissions.
2. Create a Standard API key in the Twilio Console — Account → API keys & tokens — and copy the SID and Secret. The Secret is shown once.
3. Paste the Account SID, key SID, and Secret into the app.
4. Turn on the phone numbers you want to use.
5. Send yourself a test message.
6. Optionally route a number into your HubSpot inbox so replies reach the team.

Fifteen minutes, most of it spent finding things in the Twilio Console. Our setup guide is the step-by-step version with screenshots.

If you're building it yourself instead, the honest checklist is longer: OAuth and token refresh against HubSpot, a public endpoint for Twilio's inbound webhooks with signature verification, a second endpoint for delivery status callbacks, phone number normalisation to E.164, contact search, timeline logging, and idempotency on both webhooks because both services retry. It's a couple of weeks of work and then a thing you own forever.

Mistakes we see most

Storing phone numbers without the country code. 4155550123 is not a phone number as far as Twilio is concerned. Normalise to E.164 — +14155550123 — in your CRM, not at send time. Everything downstream gets easier.

Treating "sent" as "delivered". They're different states. If your integration can't tell you which one a message reached, you're guessing.

Texting people who never opted in. In the US, marketing texts need prior express written consent, and the carriers ask to see your opt-in wording during A2P registration. This isn't a formality anyone waves through.

Ignoring STOP. Twilio blocks messages to anyone who has opted out, which means those messages show as failures. Chasing that failure by texting from a different number is the fastest way to lose a campaign registration, and in the US it carries real legal exposure.

One number for everything. If sales and support both text customers, give them separate numbers routed to separate inboxes. It costs about a dollar a month and saves a great deal of confusion — as long as your integration doesn't charge you per number.

The short version

HubSpot has no native Twilio integration. Your options are a marketplace app, a custom build gated behind Operations Hub Professional, or an automation tool that handles outbound only. Twilio carriage for a real volume of texting costs about $25 a month, so per-message pricing on top of that is a markup on the cheapest part of the stack. And whatever you choose, A2P 10DLC registration decides whether any of it delivers — start it first.

We build Twilio SMS + Workflows, a marketplace app that covers all five jobs from the list above at a flat monthly price with your own Twilio account underneath. That's our bias, stated plainly; the rest of this post is true regardless of what you install.