HubSpot in one screen
HubSpot is the all-in-one CRM most GTM teams run on: contacts, companies, deals, and the activity history that records what actually happened with each account. For an AI agent it is the system of record, the source of truth for who is in your pipeline and what state each deal is in.
Connecting Claude to it turns that record from something you read in a dashboard into something an agent can read and act on: answer a pipeline question without building a report, draft a follow-up grounded in the account's real history, or score an inbound lead and write the result back, all without you leaving the conversation.
Three ways to wire Claude to HubSpot
There are three ways to wire Claude to HubSpot. Pick by how much control you need and where the work runs.
As a connector Recommended
The simplest path. Add HubSpot as a connector in the Claude apps (Settings, then Connectors), or wire it into Claude Code. It authorizes with your own HubSpot login and inherits your permissions, so Claude sees exactly what you can see, no more. Best for reading pipeline and doing approved, one-off actions from a chat.
The API, via Claude Code or the Agent SDK
For automations that run on a schedule or at scale, call the HubSpot API from Claude Code or the Agent SDK. You own the loop, the guardrails, and the write path. This is how the recurring plays run: score every inbound overnight, enrich thin records nightly, keep the CRM clean on a cadence.
Clay as the bridge
If you already run Clay, use it as the enrichment-and-reasoning step that reads from and writes to HubSpot, with Claude as the intelligence inside it. Fastest when your data flows already live in Clay and you do not want to build a direct integration.
Read first, write on purposeWhichever method you pick, keep the read-write line firm: let Claude read contacts, deals, and activity freely, and gate the writes, creating or advancing a deal, logging a note, changing an owner, behind your approval until you trust the pattern. A wrong read costs nothing; a wrong write pollutes the system of record everyone reports on.
What connecting them gets you
- Answer pipeline questions in a sentence: which opps are stale, which are missing a next step, what moved this week, without building a report.
- Draft follow-ups grounded in the account's real HubSpot history instead of a blank page or a generic template.
- Score and route inbound leads against your ICP and write the score, tier, and owner straight back to the record.
- Keep the CRM honest: enrich thin records, flag missing owners, and dedupe, on a schedule.
What to build with HubSpot and Claude
Each of these is a full playbook or skill you can ship, wired to HubSpot.
Inbound lead enrichment & routing
Score and route inbound with an agent, then write the result back to HubSpot.
Post-call follow-up + CRM note
Draft the follow-up from the call and log the note to the deal, the moment you hang up.
Account brief skill
Pull an account's HubSpot history into a one-screen pre-call brief.
GTM automations with Claude Code + MCP
Wire HubSpot into Claude Code so the recurring plays run end to end.
Gotchas worth knowing first
- The connector inherits your permissions, so Claude cannot see or change anything you could not yourself. Connect with an account whose access matches the job.
- Gate every write to the system of record. An agent advancing deals or logging notes unattended is one stale number from polluting everyone's reporting.
- Custom properties are invisible until you name them. Tell Claude your property names and pipeline stages, or it will guess at the standard ones and miss your setup.
- Mind API limits on bulk jobs. A nightly enrichment over thousands of records should batch and back off, not hammer the API in a loop.
Claude + HubSpot: common questions
Does Claude integrate with HubSpot?
Yes. You can connect Claude to HubSpot as a connector in the Claude apps, wire it into Claude Code, or reach the HubSpot API from the Agent SDK. Once connected, Claude can read your pipeline and, with your approval, write back to it.
How do I connect Claude to HubSpot?
The simplest way is to add HubSpot as a connector in the Claude apps under Settings, then Connectors, and authorize it with your HubSpot login. For automations, call the HubSpot API from Claude Code or the Agent SDK. If you already use Clay, it can bridge the two.
Can Claude update HubSpot records, or only read them?
Both, but keep them separate in your head. Reading contacts, deals, and activity is low risk and safe to allow. Writing, creating or advancing deals, logging notes, changing owners, should stay behind your approval until you trust the pattern, because a wrong write pollutes the record.
Is it safe to let Claude write to my CRM?
With guardrails, yes. Let it read and draft freely, gate the writes behind an approval, and keep the actions reversible where you can. The connector also inherits your own permissions, so it can never reach further into HubSpot than you can.
Do I need Claude Code, or does the app work?
The Claude app plus the HubSpot connector covers most day-to-day work: pipeline questions, follow-ups, one-off updates. Reach for Claude Code or the API when you want the work to run at scale or on a schedule, like scoring every inbound overnight.