How to Connect Claude to HubSpot (5-Minute Setup Guide)

What You Need Before You Start

Three things:

  1. A paid Claude subscription. Pro, Max, Team, or Enterprise. The free tier doesn’t support connectors.
  2. An active HubSpot account. Any tier works. Free, Starter, Professional, Enterprise. There’s no HubSpot paywall for this.
  3. Super Admin or App Marketplace permissions in HubSpot. Someone with these permissions has to complete the initial setup. After that, anyone in the org can connect their own account.

That’s it. No API keys. No developer tools. No third-party middleware.

Connect Claude to HubSpot in 5 Steps

  1. Log into claude.ai and go to Settings > Connectors.
  2. Click Browse Connectors and find HubSpot under Web Connectors.
  3. Click Add to your team (or Add if you’re on a personal plan).
  4. Back on the Connectors page, find HubSpot and click Connect. You’ll get redirected to HubSpot’s OAuth screen.
  5. Log in with your HubSpot credentials, choose the account you want to connect, and grant the permissions.

That’s the setup. Claude can now read your CRM.

One more thing. Before you start prompting, go to Settings > Search & Tools in Claude and make sure HubSpot is toggled on. If you skip this, Claude won’t pull CRM data even though the connector is live.

Already set this up before November 2025? HubSpot shipped a write-access update that month. If your connector predates it, a Super Admin needs to disconnect and reconnect the integration to unlock the newer permissions. Otherwise you’re stuck with read-only access.

Set Write Tools to “Needs Approval”

This is the step most teams skip. Don’t.

Claude can now create and update CRM records. That’s powerful. It’s also the kind of thing you want a human reviewing before it goes live in your pipeline.

In your HubSpot connector settings, set Write tools to “Needs Approval.” This means Claude will draft the change and show it to you, but it won’t touch your data until you confirm.

Start there. Once your team is comfortable with how Claude handles updates, you can loosen the permissions. But day one? Keep the guardrail on.

What Claude Can Actually Do Once It’s Connected

Read access (live now):

  • Query contacts, companies, deals, tickets, line items, quotes, invoices, products, and their associations
  • Read engagement history: emails, calls, meetings, notes, tasks
  • Generate charts and visualizations from your CRM data
  • Answer questions in plain English about anything in your HubSpot

Write access (public beta):

  • Create new contacts, companies, and deals
  • Update properties on existing records
  • Log notes, tasks, and follow-up activities
  • Move deals through pipeline stages

What it can’t do:

  • Delete records. Not supported through the connector. This is a feature, not a bug.
  • Bulk operations over 10 records in a single request. Claude handles batches of 10 at a time.
  • Apply custom validation rules. If you’ve built custom property validations in HubSpot, Claude doesn’t enforce them on write. Check the data before you approve.

Permissions mirror HubSpot. Claude only sees what your HubSpot user account can see. If a rep doesn’t have access to a deal, Claude won’t surface it for them. No extra configuration needed.

Try This First

Once the connector is live, paste this into Claude:

“Show me my pipeline summary for this quarter. Flag deals over $25K with no activity in the last 14 days. For each stalled deal, tell me the last touchpoint, who owns it, and what you’d recommend as a next step.”

That’s Play 1 from the 6 AI Plays cheat sheet. You should get back a plain-English summary with deal names, dollar values, days since last activity, and a recommended next action for each stalled deal.

If Claude returns data from your CRM, you’re connected. If it asks you to set up the connector, go back to step one.

The cheat sheet has five more prompts like this. Pipeline reviews, follow-ups in your rep’s voice, lead enrichment with reasoning, rep activity audits, deal risk scoring, and objection-based content briefs. Grab all six here.

For Developers: The MCP Route

If you’re running Claude Code and want programmatic access to HubSpot from your terminal, there’s a second option: the HubSpot MCP Server.

This is the developer-oriented path. It uses the Model Context Protocol to give Claude Code direct API access to your CRM. You’ll need Node.js 18+ and a HubSpot Private App access token.

Quick setup:

  1. In HubSpot, go to Settings > Integrations > Private Apps. Create a new app and set the CRM scopes you need.
  2. Copy the access token.
  3. Add this to your Claude Code config:
{
  "mcpServers": {
    "hubspot": {
      "command": "npx",
      "args": ["-y", "@hubspot/mcp-server"],
      "env": {
        "PRIVATE_APP_ACCESS_TOKEN": "your-token-here"
      }
    }
  }
}
  1. Restart Claude Code. The HubSpot tools should appear automatically.

When to use MCP vs the connector: The connector is for your sales team. Anyone with a Claude subscription can use it, no code involved. MCP is for developers who want to build automations, run scripts against CRM data, or integrate HubSpot into their development workflow. If your team isn’t writing code, use the connector.

Is My Data Safe?

Fair question. Three things worth knowing.

Anthropic does not use your CRM data to train Claude. Data shared through the HubSpot connector is not used for model training unless your organization explicitly opts into feedback or training programs.

Permissions are inherited, not expanded. Claude can only see what your HubSpot user can see. Sensitive data properties remain inaccessible. If you have sensitive data protection enabled in HubSpot, the engagement features won’t work through the connector.

Everything is logged. All create and update actions through the connector are recorded in HubSpot’s Audit Log. You can see exactly who did what and whether it came through Claude. Full traceability.

This is also why the connector is better than your reps copy-pasting CRM data into ChatGPT. With the connector, data stays within authenticated channels with proper logging. With copy-paste, it’s in a consumer AI tool with no audit trail. If you haven’t had that conversation with your team yet, now’s a good time.

The Connector Is the Easy Part

Five minutes and Claude is reading your CRM. That’s the easy part.

The hard part is knowing which prompts actually produce useful output for your specific pipeline. Getting your team to use them consistently instead of forgetting after week one. Wiring this into daily workflows so it sticks.

That’s the gap between the tool being connected and the tool earning its keep.

If you want the setup done right and your team trained on prompts that work for your sales process, the AI Pit Crew is built for exactly this. $2,000. 30 days. Claude connected, three to five use cases wired into your workflows, prompt library handed over, team trained. You keep the system. We walk away.

Worth a 15-minute call?

Frequently Asked Questions

Does the Claude-HubSpot connector work on HubSpot Free?

Yes. The connector works across all HubSpot tiers, including Free. The only paid requirement is on the Claude side. You need a Pro, Max, Team, or Enterprise subscription. HubSpot doesn’t charge anything for the connector itself.

Can Claude delete records in my HubSpot?

No. The connector does not support delete operations. Claude can read, create, and update records, but it cannot delete anything. If you need records removed, that’s still a manual action inside HubSpot.

Is my CRM data used to train Claude?

No. Anthropic does not use data shared through the HubSpot connector for model training. The only exception is if your organization explicitly opts into feedback or training programs. All interactions are logged in HubSpot’s Audit Log for full traceability.

I set up the connector last year. Do I need to reconnect?

If you connected before November 2025, yes. HubSpot shipped a write-access update that month that added the ability to create and update records and access engagement history. A Super Admin needs to disconnect and reconnect the integration to unlock these newer permissions.

What’s the difference between the connector and the MCP server?

The connector is the no-code option. Your sales team logs into Claude, connects their HubSpot account, and starts prompting. No technical setup required. The MCP server is for developers using Claude Code who want programmatic API access to HubSpot from a terminal. It requires Node.js, a Private App access token, and a config file. If your team isn’t writing code, use the connector.

How is this different from Breeze?

Breeze is HubSpot’s built-in AI. It handles quick drafts, data enrichment, and simple automation inside HubSpot. Claude connects externally and handles deeper work: cross-record pipeline analysis, personalized follow-ups in your rep’s voice, lead enrichment with reasoning, and plain-English reporting with recommendations. Most teams that get real value from AI in HubSpot use both. We wrote a full comparison here.