How to
How to connect Claude to HubSpot for full read-write access
HubSpot ships an official Claude connector, and it genuinely covers the core: contacts, deals, logged activity. The question is what happens when your team needs custom objects, batch updates, or its own approval flow.
Connect Claude to HubSpot either with the official connector, which looks up records, creates and updates core contacts and deals, and logs activity, or with a custom MCP connector when you need more. A custom build adds custom objects, larger batch updates, and your own scoping and approval flow, authenticated as your account.
Key takeaways
- HubSpot has an official Claude connector with a standard tool set: record lookup, core contact and deal creation and updates, and activity logging.
- The gaps are custom objects, custom validation rules, larger batch updates, and your own scoping and approval flow.
- A custom connector covers those gaps with write tools like `update_deal` and `create_task`, mapped to the right record.
- It authenticates as your HubSpot account through OAuth, so Claude never gets more access than you have, and deletes stay gated.
Does HubSpot have an official Claude connector?
Yes. HubSpot ships an official Claude connector, and it covers a standard tool set: Claude can look up records, create and update core contacts and deals, and log activity. What it leaves out is custom objects, custom validation rules, larger batch updates, and a scoping and approval flow you control.
Start with the honest version: if your team lives in standard contacts and deals and mostly needs lookups plus routine updates, the official connector may be all you need. Connect it and try it first.
The friction shows up at the edges. Teams that model their business in custom objects, enforce their own validation rules, or want Claude to run larger batched updates hit the limits of a standard tool set. That is the gap a custom HubSpot connector is built for.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom HubSpot connector for Claude?
A custom HubSpot connector is built for you as a small MCP server that authenticates with OAuth using the narrowest scopes the work needs. Read tools and write tools are separated, Claude acts as your own HubSpot account, and destructive actions like deleting a record wait for your confirmation.
The path from request to working connector:
- 1Describe the HubSpot work Claude should handle, including any custom objects, pipelines, or approval rules your team relies on.
- 2We build a small MCP server with read tools (search, fetch record) separated from write tools (create, update, log).
- 3You authenticate through OAuth as your own HubSpot account, so Claude inherits your existing permissions and scopes.
- 4Claude starts working your pipeline in conversation, and destructive actions like deleting a record run only after you confirm them.
Access is revocable at any time, and the connector never holds broader scopes than the work requires.
What can Claude do in HubSpot with write access?
With full read-write access, Claude creates or updates contacts and companies, advances a deal to the next pipeline stage and updates its amount, logs calls and notes against the right record, creates follow-up tasks assigned to an owner, and opens or routes support tickets, all once you approve.
The tool set maps to the after-the-call routine most reps do by hand:
update_contactto write new details onto a contact or company record.update_dealto advance the pipeline stage and adjust the amount.log_activityto attach the call, email, or note to the right contact or deal.create_taskto set a follow-up and assign it to an owner.update_ticketto open, update, or route a support ticket.
Claude can also find every deal matching a query and propose batched updates, which is where a custom connector pulls ahead of the standard tool set on volume.
Will Claude change my HubSpot data without asking?
No. Read and write tools are separated, and destructive actions like deleting a record are gated behind a confirmation step. Claude can prepare an update and show you what it will change, but you decide which actions run automatically and which require your sign-off before touching CRM data.
In practice, most teams let record lookups and activity logging flow freely, keep routine updates fast, and reserve confirmations for deletes and anything batch-sized. The line is yours to draw.
Claude only has your access
The connector authenticates as your account through OAuth and inherits your existing permissions and scopes. It never grants Claude more access to contacts, deals, or pipelines than you already have, and you can revoke it at any time.
When is the official HubSpot connector enough, and when is it not?
The official connector is enough when your work stays in core contacts and deals with standard lookups, updates, and logged activity. It stops being enough when you need custom objects, your own validation rules, larger batch updates, or a team-specific approval flow. Those are custom-connector territory.
A quick self-test: write down the last five things you wished Claude had done in HubSpot. If they are all single-record updates on standard objects, connect the official connector today. If any involve a custom object, a bulk pass over the pipeline, or 'only after the manager approves,' the standard tool set will not carry them, and a purpose-built connector will.