How to Connect Claude to HubSpot and Set Safe Permissions

You connect Claude to HubSpot through HubSpot's built-in connector in Claude Settings, and you need a paid Claude plan. Super Admins and users with App Marketplace Access can connect without prior approval, and everyone else needs a Super Admin to approve the connector first. At Layer3Labs, we build and run AI workflows inside small and mid-sized business teams, so the permission settings below are worth choosing before anyone prompts the connector.

HubSpot recommends setting Write tools to Needs Approval before your team enters a prompt. The connector supports reading and editing standard records, but HubSpot's Knowledge Base says the connector does not support delete operations.

How to Connect Claude to HubSpot Step by Step

To connect Claude to HubSpot, open the connectors menu in Claude Settings, select HubSpot, and complete the account authentication prompt. Super Admins and users with App Marketplace Access can connect without prior approval, and everyone else needs a Super Admin to approve the connector first.

Individual users on paid Claude subscriptions can complete the setup across web, desktop, and mobile versions of Claude. Follow these seven steps to authenticate your workspace, as documented in the HubSpot Knowledge Base connector guide:

• Step 1: Click your profile icon in the bottom left corner of the Claude interface.
• Step 2: Select Settings from the navigation menu.
• Step 3: Click Connectors and select Browse to view available integrations.
• Step 4: Search for HubSpot, select it from the list, and click Connect.
• Step 5: Select and log in to the target HubSpot account when prompted by the browser window.
• Step 6: Review the requested permissions, select your options, and confirm the connection to return to your Claude chat session.
• Step 7: In each individual chat where you need CRM data, click the plus icon, select Connectors, and toggle the HubSpot switch to active.

What Claude Can Read, Create and Update in HubSpot

Claude can read, create, and update standard CRM records. Meanwhile, commerce objects (invoices, orders, carts, payments, payment links and subscriptions) and users and teams are read-only per HubSpot's Knowledge Base. The connector does not support record deletion for any object type.

The table below details data handling permissions across supported HubSpot objects:

HubSpot expanded these capabilities over time. Per the HubSpot connector changelog, the integration launched on July 29, 2025, with read-only access for standard CRM records. As of 2026-11-06, the HubSpot Features and Updates page documents multiple expansions. In July 2026, HubSpot added marketing emails for all tiers and campaign attribution data for Marketing Hub Professional or Enterprise. It also introduced quotes in public beta for Revenue Hub Professional or Enterprise, along with verified domain restrictions for Claude Enterprise. In August 2026, HubSpot enabled blog posts, custom objects, and lead creation. In September 2026, HubSpot added intent signals, answer-engine optimization (AEO) tools, saved reports, and website pages.

Settings to Choose Before the First Prompt

HubSpot recommends setting Write tools to Needs Approval, which asks for your approval before create and update changes are saved.

HubSpot recommends Needs Approval because selecting Always Allow may let edits occur without confirmation prompts in the chat. Per HubSpot's Features and Updates page, create and update changes show a preview and need your approval.

Every create and update action is recorded in the HubSpot Audit Log under the specific user and the Claude connector. Super Admins configure who can install apps and control optional data scopes. When a Super Admin updates approved permissions, individual users must disconnect and reconnect to adopt those newly authorized scopes.

Limits to Know Before Rolling It Out

The connector enforces technical constraints on batch sizes, data sensitivity, and account bindings that govern everyday prompts.

Before introducing the workflow to larger teams, evaluate these six operational boundaries established by HubSpot:

• Bulk record actions: Claude caps bulk create and update requests at 10 records at a time.
• Validation rules: Conditional property rules and pipeline stage validations apply directly to Claude updates.
• Sensitive Data protection: When the Sensitive Data setting is active in HubSpot, Claude cannot access engagement data or custom Sensitive Data properties.
• Account limits: Each Claude account connects to only one HubSpot account at a time.
• API allowances: All connector requests consume capacity against standard HubSpot Application Programming Interface (API) usage limits.
• User permissions: users see only data their HubSpot permissions allow.

When the Remote MCP Server or Claude Code Is the Better Route

Teams requiring developer scripting or automated coding workflows can bypass the user-facing connector in favor of a Model Context Protocol (MCP) server.

HubSpot documents multiple integration methods depending on whether you operate inside chat applications or developer terminal environments:

HubSpot's connector documentation does not mention Cowork or Claude Code as supported surfaces. Claude Code connects external tools with MCP per the Claude Code overview, so the MCP route belongs to developer-style builds. HubSpot's connector article does not say Claude Code can use the connector. HubSpot's MCP documentation contains inconsistencies regarding write capabilities; read the official HubSpot developer MCP page to verify current write scopes before building custom scripts.

For comparable setup logic on other accounting and business platforms, review our guide to the QuickBooks MCP server. If your team requires deeper custom data pipelines without using standard chat connectors, explore our breakdown of Claude CRM integration.

If your organization requires custom AI scoring and enrichment without direct connector exposure, consider custom architecture through a HubSpot AI CRM integration.

Who Should Not Connect Claude Yet

Teams on free Claude plans or lacking admin approval should not connect yet. Accounts needing engagement data with Sensitive Data active must also hold off.

Do not connect Claude to HubSpot if your organization falls into any of these situations:

• Teams on free Anthropic accounts cannot access the connector, as it requires a paid Pro, Max, Team, or Enterprise subscription.
• Companies that rely heavily on HubSpot Sensitive Data protections cannot access engagement data or custom Sensitive Data properties through Claude prompts.
• Organizations without a designated Super Admin or App Marketplace administrator cannot authorize installation for standard staff.

What Would Change the Answer

Three developments would change this recommendation:

• HubSpot adjusting Sensitive Data handling to permit controlled processing of engagement data.
• HubSpot's official documentation confirming support for Cowork or Claude Code environments.
• An admin policy change at your organization.

Cleaning CRM Data Before You Connect

Inaccurate, duplicate, or abandoned CRM records degrade assistant responses because Claude summarizes exactly what exists in your database.

Because the connector reads and writes what is stored in HubSpot, duplicate and stale records cause Claude to generate inaccurate summaries. For systematic audit procedures, consult our guide on CRM data cleanup.

To prepare your team, read the HubSpot Knowledge Base connector guide and request approval from your Super Admin. Then follow the setup flow to learn how to connect Claude to HubSpot with Write tools set to Needs Approval.