Skip to main content

What Claude Can Read and Change in HubSpot Through the Connector

Rob Ayala
Rob Ayala 11 min read Updated
Illustration of an AI assistant: a round orb with a spark symbol, task icons orbiting around it and a chat bubble.

Through HubSpot's connector, Claude can read contacts, companies, deals, tickets, custom objects and other listed objects, and create or update records, up to 10 at a time in bulk. It cannot delete records, it drafts workflows rather than building them, and it sees only what the connected user can see. Below is a permission map built only from HubSpot and Anthropic documentation.

Key takeaways

  • HubSpot's FAQ lists what the connector reads once turned on: contacts, companies, deals, tickets, custom objects, marketing emails, blogs, users, line items, quotes, invoices, orders, carts, products, subscriptions, and object segments with their associations.
  • Writes are create and update only, capped at 10 records per bulk change, with your conditional property and pipeline stage validation rules applied but association label validations skipped.
  • Delete is not supported, and a request for a workflow or email campaign returns drafted content that a person builds in HubSpot.
  • Claude never sees more than the connected user's HubSpot permissions allow, and a Super Admin's choice of data permissions narrows it further.
  • You need an active HubSpot user account and an active Claude account, and organization-wide action limits are documented for Team and Enterprise.
  • Our recommendation: a person confirms any bulk write, any change to a deal stage, amount, close date or owner, any association, any edit to a property that a workflow, list or report depends on, and any new contact or company.

What can Claude read and change in HubSpot, object by object?

Claude can read every object HubSpot lists for the connector and can create or update CRM records, but it cannot delete records and it drafts workflows rather than building them. The map below gives each area a source and marks anything the public pages do not confirm as not documented.

Each row assumes the base requirement in HubSpot's guide to setting up the connector: an active HubSpot user account and an active Claude account. Read access applies once the connector is turned on for your organization.

Object or areaReadCreateUpdateDeleteExtra requirementSource
ContactsYesYesYesNot supportedNone documented beyond baseHubSpot setup guide
CompaniesYesNot named (guide says “CRM records, including contacts and deals”)Not named (guide says “CRM records, including contacts and deals”)Not supportedNone documented beyond baseHubSpot setup guide
DealsYesYesYes, with pipeline stage validation rules appliedNot supportedNone documented beyond baseHubSpot setup guide
TicketsYesNot named (guide says “CRM records, including contacts and deals”)Not named (guide says “CRM records, including contacts and deals”)Not supportedNone documented beyond baseHubSpot setup guide
Other objects: custom objects, marketing emails, blogs, users, line items, quotes, invoices, orders, carts, products, subscriptions, object segmentsYesNot documented per objectNot documented per objectNot supportedNone documented beyond baseHubSpot setup guide
AssociationsYesNot documented; if made, label validations aren't appliedNot documented; if made, label validations aren't appliedNot supportedNone documented beyond baseHubSpot setup guide
Sensitive Data propertiesRead-only, if a Super Admin allows itNoNoNot supportedSensitive Data turned on; Highly Sensitive Data stays restrictedSensitive Data guide, October 2026 Rollup
Engagements in accounts with Sensitive DataRead-onlyNoNoNot supportedSensitive Data turned onSensitive Data guide
Property definitions and account settingsNot documentedNot documentedNot documentedNot supportedNot documentedHubSpot setup guide
Workflows and email campaignsNot documentedDrafted content only; you build itNot documentedNot supportedNone documented beyond baseHubSpot setup guide

In every row, the Super Admin's choice of connector data permissions and each user's HubSpot user permissions also apply.

Anything outside these rows, such as tools in other hubs, is not documented in the pages cited here. Our recommendation is to treat it as unavailable until HubSpot's guide lists it.

Digitalegy is a HubSpot partner. Companies that want help with HubSpot implementation, integrations and connecting tools like Claude can start with our HubSpot implementation service.

What should an admin check before connecting Claude to HubSpot?

Run five checks before anyone connects: the connecting user's permissions, sensitive fields, which writes need a person first, how to disconnect, and when to recheck the documentation. Each check uses settings HubSpot and Anthropic already document.

  1. Check the connecting user's permissions. The Claude Help Center article on connectors says “Claude inherits each person's permissions from the connected service,” so review the HubSpot role and team access of every user before they connect.
  2. Decide on sensitive fields. Choose whether the connector may read Sensitive Data at all. If you allow it, HubSpot's Sensitive Data guide says access is read-only and Highly Sensitive Data properties remain restricted.
  3. List the writes that need a person first. Apply the person-first write rule later in this post and set the connector's write tools to match before the first user connects.
  4. Confirm how to disconnect. Name the Super Admin who can revoke approval and uninstall the app, and plan for the documented delay: uninstall actions can take up to 30 minutes to take effect.
  5. Set a date to recheck the documentation. HubSpot's documentation for its remote MCP server, a related connector, warns that “As the MCP server's tools are updated, the available scopes may change,” so put a monthly review on the calendar.

Which write actions does the connector support, and which are not documented?

HubSpot documents two write actions, create and update, on CRM records such as contacts and deals, capped at 10 records per bulk change. Delete is not supported, and a request to build a workflow or email campaign returns a draft for you to implement.

HubSpot's setup guide states it plainly: “The connector currently supports view, create, and update actions but does not support delete operations.” The documented write behaviors are these:

  • Named objects. The guide lists creating and updating HubSpot CRM records, including contacts and deals, from the chat window.
  • Bulk cap. When creating or updating records in bulk, you can only create or update 10 records at a time. A cleanup of 240 contacts therefore means 24 separate batches, each one a point where a person can review.
  • Your validation still runs. Per the same guide, conditional property rules and pipeline stage validation rules are applied to records created or updated through the connector.
  • Association labels are not checked. Association label validations aren't applied, so a label rule your team relies on will not block a wrong association.
  • Workflows stay manual. Asked to draft an email campaign or workflow, “Claude will provide the drafted content for you to implement in HubSpot.”
  • Deletes happen in HubSpot. A person removes unwanted records directly in HubSpot, and HubSpot's audit log guide warns that “A record can only be restored within 90 days of deletion.”

Creating or editing property definitions, pipelines or account settings is not documented in the cited pages; treat those as unavailable until HubSpot documents them. If you are planning a move to HubSpot, How to Use Claude to Map Fields and Plan Data Cleanup Before a HubSpot Migration shows how to use Claude for a draft field map and cleanup rules before import.

Does Claude see more than the connected user can in HubSpot?

No. Both HubSpot and Anthropic document that the connector works inside the connected user's HubSpot permissions, and a Super Admin's data permission choices narrow it further.

“The HubSpot connector for Claude automatically respects the user permissions defined in HubSpot. This means users will only see in Claude the CRM data they’re allowed to access in HubSpot.” (HubSpot setup guide)

Three layers decide what the connector can reach, and each one narrows access rather than adding to it:

  1. HubSpot user permissions. Users can access only the data allowed by their existing HubSpot user permissions. HubSpot's MCP server documentation says the same of every action: users can only view and modify records they have access to in HubSpot.
  2. Connector data permissions. A Super Admin selects which data permissions the connector can access and who in the account can install it. After a Super Admin updates them, each user needs to reconnect to reach the newly added data.
  3. Action restrictions in Claude. On Team and Enterprise plans, Owners can limit which actions the connector takes, and the Claude Help Center article on connectors says these restrictions never grant more access than the source system permits.

The same article adds that if someone can't access a specific file, channel, or record in the source system, the connector can't reach it from Claude either.

For a weekly use of the connector, How to Use Claude to Review HubSpot Pipeline Data and Flag Forecast Risk Every Week has five prompts that flag slipped close dates, stalled deals and missing fields by owner. Marketing ops teams can open How to Use Claude to Analyze HubSpot Campaign and Attribution Reports for four monthly prompts and the CSV export alternative.

Which Claude and HubSpot plans do you need for the connector?

HubSpot's setup guide requires an active HubSpot user account and an active Claude account. The HubSpot pages cited here name no required HubSpot tier, and organization controls for connectors are documented for Claude Team and Enterprise.

Claude planListed seat priceWhat matters for the connector
Pro$20 a month billed monthly, or $200 billed up front for a yearNot stated in the pages cited here; organization controls are documented for Team and Enterprise
MaxSee Anthropic's pricing pageNot stated in the pages cited here
Team$25 per seat a month billed monthlyAn Owner or Primary Owner enables connectors; Owners can limit connector actions organization-wide
EnterpriseUS$20 per seat a month (seat price), billed annually, 20 seat minimumTeam controls plus audit logs, with exports covering the past 180 days

Prices are as listed on Anthropic's pricing page. The admin controls come from the connectors article, and the audit logs article states that audit logs are available for Enterprise organizations only. The pricing page shows Enterprise in US dollars, so buyers in Canada should confirm the billing currency for every plan at checkout.

For HubSpot's remote MCP server, a separate connector, the developer documentation notes that “Tool availability varies by HubSpot subscription, user permissions, and account configuration.” Reading Sensitive Data also requires an account that has Sensitive Data turned on, per the October 2026 Rollup.

How do you set up the connector, limit it and disconnect it?

A HubSpot Super Admin decides what the connector may access and who may install it, and on Claude Team or Enterprise an Owner enables it and can restrict its actions. Removing access is a revoke in HubSpot, and uninstalls can take up to 30 minutes.

  1. Enable it in Claude (Team and Enterprise). Before members can use connectors, an Owner or Primary Owner needs to enable them for the organization, per the Claude Help Center.
  2. Allow it in HubSpot. A Super Admin selects which data permissions the connector can access and who in the account can install it, as the setup guide describes. Note that required data permissions for apps cannot be modified or turned off.
  3. Connect each user. Each user connects with their own HubSpot user account.
  4. Restrict writes. On Team and Enterprise plans, Owners can limit which actions a connected service can take across the organization, per the same Help Center article. For each permission category or individual permission, select Always allow, Needs approval, or Blocked. Choose Needs approval for write tools.
  5. Reconnect after changes. When a Super Admin widens data permissions, each user reconnects before the new data appears.

To limit or remove access, a Super Admin can revoke approval, which removes access to apps that were previously approved. Uninstall actions can take up to 30 minutes to take effect, so revoke first, wait, then confirm in Claude that the connector no longer returns HubSpot data.

Teams already on HubSpot that need ongoing HubSpot support can go to our HubSpot support page.

What are the data risks, and which writes should a person check first?

The main risks are wrong updates spread across many records, associations that skip label checks, sensitive fields exposed to more people than needed, and an audit trail you have not yet tested for connector changes. Our rule: a person confirms any bulk write, any change to a deal stage, amount, close date or owner, any association, any edit to a property that a workflow, list or report depends on, and any new contact or company.

Any tool that writes to your CRM writes into data that many teams already distrust. In Validity's report The State of CRM Data Management in 2025, 37% of CRM users reported losing revenue as a direct consequence of poor data quality, and 76% said less than half of their organization's CRM data is accurate and complete.

HubSpot's best practices in the setup guide point the same way: “Start small by updating a single record before making bulk changes,” and “Always review the changes proposed by Claude before confirming them.”

The person-first write rule

This is our recommendation, built on those two lines. A person confirms the change before anything is written when it:

  • touches more than one record, including any bulk batch up to the 10-record cap;
  • changes a deal stage, amount, close date or record owner;
  • creates or edits an association, because association label validations aren't applied;
  • edits a property that a workflow, list or report depends on;
  • creates a new contact or company, which can duplicate an existing record.

Keep Sensitive Data access off unless a specific use case needs it. For the audit trail, HubSpot's audit log lets you review, filter, and export a record of user actions in a HubSpot account, but “The log only records HubSpot-user based actions,” so run one test update and confirm how connector changes appear before relying on it. On the Claude side, audit logs are Enterprise only and an export covers the past 180 days.

How do you check whether a connector capability has changed?

Treat the documentation as dated: reread HubSpot's setup guide and developer changelog each month, have each user reconnect after a Super Admin updates data permissions, and retest on a single record. HubSpot widened connector access in its October 2026 changelog, so this is not hypothetical.

HubSpot's October 2026 Rollup announced that Super Admins can now allow supported AI connectors to read Sensitive Data, and said: “Until now, AI connectors couldn’t access Sensitive Data properties or engagements.” For HubSpot's remote MCP server, a separate connector, the developer documentation adds that, in the event of scope updates, users who have already installed the connector will need to re-install to grant any new scopes.

Our recommended monthly routine:

  1. Open the setup guide and compare its date with your last review.
  2. Scan HubSpot's developer changelog rollup for AI connector entries.
  3. If scopes changed, ask a Super Admin to update data permissions and have each user reconnect or reinstall.
  4. Run one create and one update on a test record and confirm your validation rules still apply.
  5. Update the permission map above, and change a “not documented” cell only when a public page confirms it.

Frequently asked questions

Does the 10-record limit apply when Claude reads data?

HubSpot documents the cap for writes: when creating or updating records in bulk, you can only create or update 10 records at a time, per the setup guide. The pages cited here state no equivalent per-request cap for reading.

Can one Claude account connect to several HubSpot portals?

Not at the same time. The setup guide says you can only connect one HubSpot account at a time to a single Claude account.

Why can't Claude see a property I can see in HubSpot?

Check two things: whether the connector's data permissions include it, and whether you reconnected after a Super Admin changed those permissions. The setup guide says each user will need to reconnect the connector to gain access to the newly approved data.

Can Claude log notes or calls in an account with Sensitive Data turned on?

No. HubSpot's Sensitive Data guide says “However, engagements are limited to read-only access in accounts with Sensitive Data.”

Sources

  1. Set up and use the HubSpot connector for Claude, HubSpot (November 20, 2026)
  2. Configure AI connector access to Sensitive Data and engagements, HubSpot (November 12, 2026)
  3. October 2026 Rollup, HubSpot (October 30, 2026)
  4. Use connectors to extend Claude's capabilities | Claude Help Center, Anthropic (November 18, 2026)
  5. Manage access to apps, HubSpot (October 20, 2026)
  6. Integrate AI tools with the HubSpot MCP server - HubSpot docs, HubSpot (November 20, 2026)
  7. View and export account activity history, HubSpot (October 30, 2026)
  8. Plans & pricing | Claude by Anthropic, Anthropic
  9. Access audit logs | Claude Help Center, Anthropic (June 15, 2026)
  10. The State of CRM Data Management in 2025, Validity (January 29, 2026)

Want help putting this into practice?

Don't forget to share this post!

Rob Ayala

Rob Ayala

CEO & Founder

Related posts

HubSpot Integration Implementation HubSpot

HubSpot Integration Method: Native App, Data Sync or Custom API?

Rob Ayala
HubSpot Marketing Operations AI

How to Use Claude to Analyze HubSpot Campaign and Attribution Reports

Rob Ayala
HubSpot Implementation AI

How to Use Claude to Map Fields and Plan Data Cleanup Before a HubSpot Migration

Rob Ayala