A plain language explainer for connecting Claude to your HubSpot CRM. What it can read, what it can write, how to install it, and what tends to get in the way.
A paid Anthropic plan on one side, any HubSpot tier on the other. That is it.
Twenty dollars per month, per user. Good for one or two people trying it out.
Per seat, with admin controls and a Data Processing Agreement. The sensible choice for the Lex Mundi HQ marketing and BD team.
SSO, SCIM provisioning, organization-wide audit logs, and Zero Data Retention. The step up once Claude is a real workflow tool across the team.
The Connector works on every HubSpot subscription, including Starter. No upgrade needed on the HubSpot side.
The Connector gives Claude access to almost every standard HubSpot object and the ability to create or update a controlled subset of them.
Anything visible in the HubSpot UI to the user, Claude can summarize, compare, search, and rewrite.
The Connector intentionally blocks all engagement data (calls, meetings, notes, emails) when the HubSpot account has the Sensitive Data feature switched on. Most "know every guest" and "engagement snapshot" prompts then return nothing, and it looks like Claude is broken. Before the first demo, check whether Sensitive Data is on at the account level.
There are clear limits, designed for safety. Some can be worked around with a small custom build sitting on top.
The Connector cannot delete records. Removing data still happens in HubSpot. Often a feature, not a bug.
Only published landing pages and blog posts are visible. Anything still in draft inside HubSpot stays hidden.
Validation logic defined inside HubSpot forms does not apply during writes through the Connector. Property-level rules still do.
Member-firm-shaped data lives in custom objects (jurisdictions, referrals, member events). The off-the-shelf Connector cannot reach those today.
Workable with a small custom buildThe 10-record cap is per request. Operations across hundreds of contacts need batching or a workflow.
Workable with a small custom buildCustom properties flagged as Sensitive Data are excluded by design. Engagements are blocked entirely when Sensitive Data is on account-wide.
One short flow inside HubSpot. After that, a small per-user setting in Claude decides whether write actions need approval each time or run on their own. Total time, under ten minutes.
Click through every step in a guided pop-up. One step at a time, with the exact buttons to press and the things to watch out for.
Each colleague at Lex Mundi HQ then connects through their own Claude account, and the Connector respects each person's HubSpot permissions automatically.
The Connector does not overwrite HubSpot's user permissions. Whatever a colleague can see in HubSpot is what they see through Claude. The Connector is bound to their personal login.
Drawn from teams that have already gone through their first install.
The Super Admin installed the Connector but forgot to click Give users access in HubSpot Settings, Integrations, Connected Apps. Colleagues then see no-permission errors.
If the HubSpot account has the Sensitive Data feature enabled, engagement data is silently excluded. Teams notice this only when Claude says it found no calls or emails.
Claude is strong at language and middling at exact arithmetic. Pipeline values, contact counts, conversion rates: it sometimes rounds, sometimes truncates large result sets silently.
Each stage can be rolled back the same day. Move to the next one only when the previous one has earned the team's trust.
Super Admin installs with read-only scopes. One or two Claude Team seats. Run the Ideas prompts, document what works. Nothing in HubSpot changes. Reversible by disconnecting at any point.
Re-authorize with write scopes for contacts, deals, engagements. Set every write tool to Needs Approval. Roll out to three to five HQ users. Watch the HubSpot Audit Log weekly for the first month.
Upgrade to Claude Enterprise for SSO, SCIM, organization-wide audit logs, and Zero Data Retention. Open the Connector up to events, membership, and content colleagues alongside marketing and BD. Move to custom builds once the team is fluent.
If Sensitive Data is enabled at the account level, the Connector silently blocks all engagement data (calls, meetings, notes, emails). Half of the Ideas prompts then return empty results and the pilot looks broken. Ask your HubSpot admin to confirm before the first demo.