I’m trying to connect the HubSpot connector for Claude. When I click Connect in Claude, HubSpot’s sign-in page shows “Choose an account,” but the list is empty: “No accounts match that search.”
I’m signed in to HubSpot, and my account is hosted in the NA3 data center (app-na3.hubspot.com).
The same thing happens when I click Connect from the connector’s Marketplace listing inside my account.
app.hubspot.com/myaccounts-beta says I’m “not in any HubSpot portal,” but app-na3.hubspot.com/myaccounts-beta lists my account.
It looks like the connector’s account picker isn’t finding NA3 accounts. Is there a fix or workaround?
Your clue is solid: the picker is resolving against the default app.hubspot.com account list, while your portal only shows under NA3. That is why myaccounts-beta on app is empty and NA3 is correct.
Work the connection as a regional-session problem before you blame Claude itself:
Confirm the portal host everywhere. In an incognito window, sign in only via https://app-na3.hubspot.com and open the connector / Marketplace install from that host. Do not bounce through app.hubspot.com mid-flow. Mixed hosts are a common way to get an empty “Choose an account” list.
Clear HubSpot SSO cookies for both hosts, then retry. Sign out of HubSpot completely, clear cookies for hubspot.com / app.hubspot.com / app-na3.hubspot.com, close the browser, reopen, sign in on NA3 first, then click Connect from Claude. Stale default-shard cookies often make the picker search the wrong account set.
Check you are a user on that portal with permission to install / authorize apps. Super Admin or App Marketplace install rights matter. If your user exists only on another portal, NA3 will not appear in the OAuth chooser even when the company “has” an NA3 account.
Try the Marketplace connect from inside the NA3 portal, then the Claude side. You already saw both fail; after a clean NA3-only session, retry Marketplace first. If Marketplace still opens an empty chooser, the connector’s OAuth redirect is likely pinned to the global account picker and not enumerating NA3.
Escalation packet (this is the useful bit for HubSpot / Anthropic). Include: portal id, NA3 host, screenshot of empty chooser, screenshot of NA3 myaccounts-beta listing the portal, screenshot of app.hubspot.com myaccounts-beta saying you are in no portal, exact Claude connector name/version, and that Connect was tried from both Claude and Marketplace. Ask explicitly whether the HubSpot-for-Claude OAuth client supports NA3 (and other regional) account discovery.
Stabilize ownership while blocked. Do not create a second workaround portal on a different shard just to satisfy the picker. That splits CRM ownership. Keep NA3 as system of record; treat this as a connector regional bug until Support confirms otherwise.
So: empty picker + NA3-only myaccounts almost always means the OAuth account list is searching the wrong shard/session. Clean NA3-only login first, then escalate with the app vs NA3 myaccounts contrast if it still fails.
If you can add the HubSpot portal id (and whether any non-NA3 portals show under the same login), the next check is obvious.
Your NA3 observation is the key clue here. The fact that your portal appears on the app-na3 version of myaccounts-beta but not the standard version makes me suspect the connector’s account picker may be looking in the wrong region, rather than there being an issue with your account or permissions.
Two quick things worth trying:
Sign in through a private window (or a different browser) to rule out a cached session pointing to the wrong region.
Disconnect and reconnect the connector from Settings → Connectors → HubSpot.
If the picker is still empty after that, I don’t know of a client-side workaround. I’d report it to both HubSpot Support and Anthropic Support, including your portal ID, the fact that the portal is hosted on NA3, and screenshots showing the difference between the two myaccounts-beta pages. That should give them enough context to investigate whether there’s a regional issue with the connector.
If you hear back from either team or find a workaround, it would be great to post the update here - it could help others running into the same issue.