Skip to main content
You send iMessage from HubSpot by connecting HubSpot to Tuco AI, which syncs your HubSpot contacts and then sends real iMessage (blue-bubble) texts on your behalf — with automatic SMS fallback for contacts who aren’t on iMessage. HubSpot has no native iMessage channel, so you need a bridge like Tuco. There are two ways to trigger the send: build a sequence inside Tuco using your synced HubSpot contacts (no code), or fire a Tuco send from a HubSpot workflow with a webhook action.

​
Why HubSpot can’t send iMessage on its own

HubSpot sends email and SMS (via integrations), but it cannot send iMessage — iMessage runs only through Apple’s network from a signed-in Apple ID. Tuco AI provides Apple-connected sending “lines,” so HubSpot becomes the system of record and Tuco becomes the iMessage sending layer.

​
Method 1 — Connect HubSpot and send from a Tuco campaign (no code)

Best for bulk outreach and follow-up sequences.
1

Connect HubSpot

In Tuco go to Integrations → CRM → Connect with HubSpot and authorize via OAuth (about 30 seconds). A full contact sync starts automatically; after that, Tuco pulls contacts modified in HubSpot every 15 minutes and deduplicates by phone number.
2

Check iMessage availability

Tuco automatically checks whether each synced contact can receive iMessage, so blue-bubble-eligible contacts are messaged over iMessage and the rest fall back to SMS. See Check iMessage availability.
3

Build and launch a campaign

Create a campaign with your message, personalization variables, and schedule. Use HubSpot properties (like lifecyclestage) as live stop conditions and branches — every check calls the live HubSpot API, not stale cached data.

​
Method 2 — Trigger an iMessage from a HubSpot workflow

Best for real-time, event-driven sends (e.g. “text me when a deal reaches Stage 2”). This uses HubSpot’s Send a webhook workflow action, available on HubSpot Operations Hub / Professional tiers. On plans without the webhook action, use a Custom Code action or Method 1 instead.
  1. In your HubSpot workflow, add a Send a webhook action — method POST, URL https://app.tuco.ai/api/messages.
  2. Add header Authorization: Bearer tuco_sk_xxxxxxxxxxxxx (your Tuco API key).
  3. Send a JSON body with the contact’s phone (or email) and your message. Optionally pin a sending line with lineId or add attachmentUrls. Full field reference: Send Message API.
Tuco runs the iMessage availability check and SMS fallback automatically, so you don’t have to branch on channel inside HubSpot.

​
What syncs between HubSpot and Tuco

Owner mapping means messages are attributed to the right rep, and message activity can be logged back to the HubSpot contact timeline. See the full HubSpot integration reference.

​
Frequently asked questions

No. HubSpot cannot send iMessage on its own. Tuco AI is the bridge — it connects to HubSpot via OAuth and sends real iMessage texts from Apple-connected lines, with SMS fallback.
Only for Method 2 (the webhook-triggered send), which relies on HubSpot’s “Send a webhook” workflow action. Method 1 — syncing contacts and sending from a Tuco campaign — works on any HubSpot tier.
Tuco checks iMessage availability before sending and automatically routes non-iMessage contacts to your configured SMS fallback, so the message still lands. See failures and fallbacks.
Yes. HubSpot properties can be used as live stop conditions and branches in Tuco campaigns and Goal Bots — each check queries the live HubSpot API.

Connect HubSpot

Full HubSpot setup: sync, owner mapping, property mapping, and campaign conditions.