If you already run your pipeline in HubSpot, the obvious move is to turn on HubSpot's own SMS add-on and text contacts straight from a workflow. For a lot of businesses that works fine. For payday lenders, cannabis and CBD retailers, crypto platforms, debt collectors, credit repair shops, and third-party lead-gen operations, it does not work at all, because HubSpot's SMS product runs on Twilio, and Twilio will not carry that traffic regardless of how the workflow is built.
This is a walkthrough of why the native add-on rejects those contacts, and how to wire HubSpot to a phone-based SMS gateway instead, using nothing but the webhook actions HubSpot already ships.
Why HubSpot's Native SMS Won't Text These Contacts
HubSpot's own setup documentation says plainly that not every business can use the feature: "Not all businesses can send SMS. You'll need to make sure your business doesn't fall under one of the restricted categories," and it points operators to Twilio's Forbidden Message Categories list, because Twilio is the carrier pipeline underneath HubSpot's SMS marketing feature.
That Twilio list is specific. It forbids payday loans, short-term loans, and cryptocurrency promotion under "high-risk financial services." It forbids cannabis, CBD, and other regulated substances outright, even in states where they're legal to sell. It forbids third-party debt collection, debt consolidation, and credit repair. It forbids third-party lead generation, meaning any business that gathers or shares consumer contact information on someone else's behalf. If your business fits any of those descriptions, HubSpot's own SMS tool is closed to you before you write a single message, no matter how clean your consent records are.
This isn't a HubSpot decision so much as an inherited one. HubSpot sits on top of A2P 10DLC, the U.S. carrier-mandated business-messaging registry, and 10DLC gates traffic by declared industry, not by message content. A perfectly compliant payment reminder from a licensed lender gets the same rejection as a scam text, because the carrier filter never reads the message. It reads the business category.
What "Marketing SMS" Actually Restricts Inside HubSpot
Even for businesses HubSpot will approve, the native add-on is narrower than it sounds. It's a paid add-on layered on top of a Marketing Hub Professional or Enterprise subscription, which starts at $800 a month before the SMS add-on is even added. It provisions a single 10DLC phone number per account, sends only to U.S. and Canadian +1 numbers, and is scoped to marketing contacts specifically: sole proprietors can't use it, sales reps can't send from deal records or sequences, and every recipient has to already be an opted-in marketing contact in HubSpot's own object model. It was built for campaign blasts, not for the back-and-forth conversations a lending or collections operation actually needs.
The Workaround: Route HubSpot Sends Through a Phone Instead of a Campaign
Android Texter sends SMS through a real, user-owned Android handset on a real carrier line, so the traffic is person-to-person SMS, the same category as texting a friend, rather than application-to-person traffic filed under a registered campaign. A2P 10DLC gating, including Twilio's forbidden-category list, applies to A2P traffic. It doesn't apply to a message sent from a phone.
That's the whole mechanism, and it's worth being precise about what it does and doesn't do. It removes the carrier-level category gate. It does not touch the Telephone Consumer Protection Act, which governs who you can text and what you can say to them regardless of which pipe the message travels through. Consent, recordkeeping, and honoring opt-outs are the operator's responsibility either way.
The bridge itself is two HubSpot workflow features stitched to Android Texter's REST API: a webhook action going out, and a webhook trigger coming back in.
Setting Up the Outbound Webhook
- Generate an Android Texter API key. From the dashboard at /dashboard/settings/api-keys, create a key (it will be prefixed
atx_). This gets sent as theX-API-Keyheader on every request. - Build or open the HubSpot workflow that should trigger a text (a deal stage change, a form submission, a payment-due date property). HubSpot's webhook action is available in contact-based workflows on a Data Hub Professional or Enterprise subscription, per HubSpot's own webhook documentation.
- Add a POST webhook action pointed at Android Texter's send endpoint (
POST /api/v1/messages/send), with theX-API-Keyheader set to your key. Map the contact's phone number and your message text into the request body using HubSpot's contact-property merge fields, the same way you'd populate an email template. - Test it. HubSpot lets you fire the webhook against a single record without affecting live workflow enrollment, so you can confirm delivery before turning it on for the full list. Android Texter's interactive Swagger UI at /api/swagger is useful here to see the exact payload shape before you build the HubSpot side.
- Turn on scheduled sends where the workflow calls for it. The send endpoint accepts an RFC 3339 timestamp, so a payment-due reminder or an appointment nudge can queue for a specific time rather than firing the moment the workflow runs.
For high-volume lists, Android Texter's API accepts a broadcast of up to 500 phones in a single call, and multi-device pairing lets sends distribute across several paired phones rather than one line absorbing the entire load.
Getting Replies Back Into HubSpot
Outbound is the easier half. Getting a reply to show up against the right HubSpot record takes one more piece: HubSpot's "when a webhook is received" workflow trigger, also gated to Data Hub Professional or Enterprise. It generates a unique HubSpot URL that, when it receives a JSON POST matching a property you've marked as unique (the contact's phone number is the natural choice), enrolls or re-triggers a workflow on that exact contact record.
On the Android Texter side, register that HubSpot URL as a webhook endpoint (POST /api/v1/webhooks) subscribed to the message.received event. Android Texter will return a signing secret when you register it, which lets you verify each delivery is genuinely from Android Texter via HMAC before you let it touch a HubSpot record. Every inbound text then lands on the matching contact, where a workflow can update a "last SMS reply" property, create a task for a rep, or fire a Slack notification, all without anyone manually copying a phone number between two systems.
This isn't a native two-way sync the way a purpose-built HubSpot app would be. It's a webhook relay, and it takes maintaining that one mapping property. For a single number handling a manageable inbound volume, that's a small setup cost against getting a channel at all.
What This Bridge Doesn't Change
Android Texter doesn't grant clearance to text anyone. Prior express consent is still required for non-emergency marketing texts to a wireless number, and TCPA penalties (up to $500 per violation, $1,500 if willful) apply the same as they would through any other channel. STOP, UNSUBSCRIBE, CANCEL, END, and QUIT all still have to trigger suppression, whatever system is sending the message. What changes is that a compliant, consented message from a lending, cannabis, or collections operator no longer gets stopped by a carrier filter that never looks at the content in the first place, it looks at the industry code.
It's also worth being honest that this setup costs more than flipping on HubSpot's native toggle for businesses HubSpot actually allows. You're paying for Data Hub Professional or Enterprise to unlock the webhook features on both ends, on top of whatever Marketing or Sales Hub tier you're already running. For an approved, low-volume marketing use case, HubSpot's own add-on is simpler. This bridge earns its keep specifically for the businesses HubSpot's category list locks out entirely.
Frequently Asked Questions
Does this replace HubSpot's native SMS add-on?
Only if you need it to. If your business isn't on Twilio's restricted list and you only need marketing blasts to opted-in contacts, HubSpot's add-on is simpler to set up. This bridge exists for businesses the add-on won't serve at all, or that need two-way conversations and sales-side texting the add-on doesn't offer.
Do I still need consent to text contacts imported into HubSpot?
Yes. Routing through a phone instead of a campaign changes which carrier rule applies to the message, not whether the TCPA applies. You need prior express consent for marketing texts and a record of how you got it, exactly as you would with any SMS provider.
What HubSpot plan do I need for this specific setup?
Both the outbound POST webhook action and the inbound "webhook received" trigger require Data Hub Professional or Enterprise. You'll also need whichever Marketing or Sales Hub tier already runs your workflows and contact records.
Will replies show up on the HubSpot contact timeline automatically?
Not out of the box. The inbound webhook enrolls or updates the matching contact record, and from there a workflow action can log a property, create a task, or notify a rep. It's a relay you configure, not a native app with built-in timeline logging.
Can I use this for cold outreach to a purchased list?
No. Removing the carrier's industry gate doesn't remove the TCPA's consent requirement. A phone-based channel makes compliant messages deliverable that a carrier filter would otherwise block on category alone; it doesn't make an unconsented list safe to text.
If HubSpot's own SMS tool has told you your business isn't eligible, the fix isn't a different CRM. It's a channel that doesn't ask Twilio's permission first. Android Texter plugs into the same workflow and webhook tools you're already using in HubSpot, it just sends through a phone instead of a registered campaign.