HubSpot MessageBlue Integration Troubleshooting

Every status message, what it means, and the FAQ
View as Markdown
Private beta

The MessageBlue HubSpot integration is in private beta and is not enabled on every account yet. Ask your MessageBlue administrator or support team for access.

What the status line is telling you

The Status field on Settings → HubSpot CRM has three states, and they fail for completely different reasons. Read it before changing anything.

StatusMeaningWhat to do
HubSpot service is not configured on the backend yet.Nothing to do with your portal — the MessageBlue backend has no HubSpot service configured, so Connect HubSpot is disabledContact MessageBlue support. No amount of reinstalling in HubSpot will change this
Not connected. Connect once to link this app to HubSpot.MessageBlue is ready; this app simply has no portal linked yetFollow set up HubSpot
Connected (with a Portal ID)The app is linked to that portal and tokens are refreshingNothing — verify with the quick test

The first row is the one people misdiagnose. A disabled Connect HubSpot button always means the backend is not configured — it never means your HubSpot permissions are wrong.

Authorization pages

HubSpot’s own tab shows the outcome of the OAuth flow directly:

PageCauseFix
✅ Connected to HubSpot!Success. Lists your Portal ID and MessageBlue App IDReturn to MessageBlue — status refreshes when the tab regains focus
❌ Authorization FailedHubSpot rejected the request, usually a declined consent or an account without install rightsRetry as a user who can install apps on that portal
❌ No Authorization CodeThe flow was interrupted before HubSpot issued a code — most often the tab was closed earlyStart again from Connect HubSpot and let it finish
❌ Connection FailedHubSpot approved, but the token exchange or install record failedRetry once; if it persists, contact support with your App ID and the time it happened

Symptoms

In order of likelihood:

  1. The flow did not finish. Reopen Connect HubSpot and complete it without closing the tab.
  2. You authorized a different portal from the one you installed into. Use Reconnect HubSpot and pick the right portal.
  3. The page has stale state. Status refreshes when the MessageBlue tab regains focus — click Refresh status to force it.

Work outwards from MessageBlue:

  1. Is the Mac agent online? No agent, no messages in either direction. Check the Online indicator on your dashboard.
  2. Is MessageBlue a channel on the inbox you are watching? Confirm it in Conversations → Inbox settings, and check your inbox filters are not hiding it.
  3. Send a known-good test with New conversation — that proves the MessageBlue half independently of anything inbound.

Two causes, both easy to miss:

  • The Mac agent is offline. HubSpot will still accept and display your reply, so the thread looks healthy while nothing is delivered.
  • You replied on the wrong channel. A contact with email or SMS history will happily accept a reply on those channels instead. Confirm the thread you are typing into is the MessageBlue one.

HubSpot matches threads to contacts by phone number, so formatting decides identity. Use full E.164 everywhere — +15551234567, not (555) 123-4567.

If the same person already exists in your CRM under several number formats, merge those contacts in HubSpot; otherwise the thread attaches to whichever record matched first.

Expected on a first contact from an unrecognised number. MessageBlue passes the phone number; HubSpot matches or creates the contact from it, so the name fills in once a CRM record exists and matches.

The New conversation fields stay disabled until a portal is connected — the hint under the button says so. Connect first. If the button is active but the send fails, the error toast carries the reason.

Uninstalling the MessageBlue app in HubSpot removes the install record while MessageBlue still shows the old connection. Reinstall in HubSpot, then Reconnect HubSpot in MessageBlue.

Frequently asked questions

No. MessageBlue holds the app credentials. You never paste a HubSpot secret into MessageBlue — if a guide tells you to, it is not this integration.

No. Tokens refresh automatically once connected. You reconnect only to change portals or after uninstalling the app in HubSpot.

No — the mapping is one app to one portal. Connecting a second portal replaces the first. Use a separate MessageBlue app per portal.

Yes. They are independent, and both can be active on the same app. See how the routes compare.

Yes. If the agent is deployed it answers as normal, and the exchange still syncs to HubSpot. If a teammate also replies in HubSpot, the customer gets two messages — decide who owns the conversation.

E.164 with the country code — +15551234567. Anything else risks attaching to the wrong contact.

Uninstall the MessageBlue app in HubSpot, and/or connect a different portal from MessageBlue Settings.

Getting help

When contacting MessageBlue support, include:

  • Your MessageBlue App ID — from Settings → HubSpot CRM or API & secrets
  • Your HubSpot Portal ID — shown on the success page, or in your HubSpot account settings
  • Which direction failed: Connect, inbound, or HubSpot reply
  • Roughly when it happened, with the timezone