Put HubSpot to Work With Claude
Your company already has valuable information inside HubSpot.
Agency Growth helps connect approved HubSpot information and workflows to Claude so employees can find context, prepare work, update processes and complete recurring tasks without manually moving information between systems.
Connection method: HubSpot publishes an official connector for Claude: you add it from the connectors directory in Claude's settings, sign in to HubSpot, and approve the permissions it requests; it currently requires a paid Claude plan and works with HubSpot accounts on any tier.
What information moves between the systems
Inside HubSpot
- Contacts and companies, with their properties and ownership
- Deals and pipeline stages
- Support tickets
- Products, line items, quotes, invoices, and orders
- Engagement history: emails, calls, meetings, notes, and tasks
- Marketing lists, campaigns, and marketing events
- Published landing pages, website pages, and blog posts
- Users and teams, so activity maps to real owners
What Claude can read
- CRM records the connected user is allowed to see, including contacts, companies, deals, tickets, line items, quotes, invoices, orders, products, and subscriptions
- Engagement history on those records: emails, calls, meetings, notes, and tasks
- Marketing data such as lists, campaigns, marketing events, and published landing pages, website pages, and blog posts
- Users and teams data, useful for questions like which rep owns an account
- Access is scoped by HubSpot permissions: each person sees only the records their own HubSpot account can see
Actions that may be supported
- Creating and updating contacts, companies, deals, tickets, line items, and products
- Logging engagement activities: calls, meetings, notes, tasks, and emails
- Drafting follow-up emails and summaries from CRM context for a person to review and send
- Bulk creates and updates in small batches: HubSpot documents a limit of 10 records per operation
- Requesting approval before a change executes, so a person confirms writes before they land
- Deleting records is not supported through the connector, and additional actions may be supported as HubSpot and Anthropic expand the integration
Permission and access considerations
- The connector respects HubSpot permissions: employees see in Claude only the CRM data their HubSpot account already allows
- Initial setup requires a HubSpot Super Admin or a user with App Marketplace permissions, who can then grant access to other users
- You review and approve the specific permissions the connector requests when you connect it
- We recommend least privilege: connect the fewest users needed first, confirm behavior, then expand
- Every action taken through the connector is attributed in HubSpot's audit log to both the user and the Claude connector
What teams build on Claude + HubSpot
Preparing account briefs before sales calls, pulling recent activity, open deals, and past conversations into one summary
Summarizing pipeline status before the weekly sales meeting, by stage, owner, and recent movement
Drafting follow-up emails from the notes of the last call or meeting, ready for the rep to edit and send
Logging call notes and creating follow-up tasks after a customer conversation, with approval before anything is written
Reviewing open tickets and recent complaints for an account before a renewal conversation
Cleaning up contact and company records in small approved batches: filling gaps, fixing formatting, standardizing fields
Turning meeting outcomes into proposed deal-stage updates and next-step tasks for a rep to confirm
Pulling campaign and published-page context into a marketing review so the team starts from the same facts
Setup requirements and human checkpoints
Setup requirements
- An active HubSpot account; HubSpot states the connector works across its products and plans
- A paid Claude plan; HubSpot currently lists Pro, Max, Team, and Enterprise as supported
- A HubSpot Super Admin or a user with App Marketplace permissions to make the initial connection
- A decision about which users get access and which permissions the connector is granted
- Written rules for what Claude may update in the CRM and what always requires human approval
- A short pilot with one team before rolling access out more broadly
Human approval points
- Any create or update to a CRM record: the connector can ask for approval before a change executes, and we configure workflows so it does
- Any customer-facing text: emails and messages are drafted by Claude and sent by a person
- Deal-stage changes, since they drive forecasts and reporting
- Bulk record updates, even within the 10-record limit, get a human check before running
- Any change to how the connector is scoped: new users, new permissions, or reconnection to a different HubSpot account
Limitations and security considerations
Limitations
- Custom objects are not available through the connector
- Custom validation rules are not applied when records are created or updated through it, so bad data can get in if nobody reviews writes
- Only published content is accessible: draft pages and posts are not
- Bulk operations are capped at 10 records at a time, so it is not a mass data-migration tool
- Records cannot be deleted through the connector
- One HubSpot account can be connected to a Claude account at a time
- If HubSpot's sensitive data feature is enabled, the connector does not access engagement data
- Capabilities may change as HubSpot and Anthropic update the connector, so we verify current behavior during implementation
Security considerations
- Access is permission-scoped: an employee cannot see records in Claude that their HubSpot account cannot see
- Actions are logged: HubSpot's audit log attributes connector activity to the specific user and to the connector
- Anthropic's published policy states it does not use data shared through the connector to train its models except in cases like opt-in or submitted feedback; confirm the current policy for your plan during setup
- Grant the narrowest permissions that support the workflows you actually run, and review connected users on a schedule
- Disconnect access promptly when an employee leaves or changes roles
- If your HubSpot account holds regulated or sensitive data, review HubSpot's sensitive data settings before connecting
If the native path is not a fit
- A custom integration through the HubSpot API, built as a private connection with exactly the scopes and guardrails you specify, when the native connector's permissions or limits do not fit
- Scheduled exports of approved HubSpot reports loaded into a shared Claude workspace as reference material, when you want read-only context with no live CRM connection
- Middleware automation platforms that pass data between HubSpot and Claude through their APIs, when the workflow needs triggers the connector does not provide
- A phased approach: start with curated, read-only context, prove value, then move to the live connector once approval rules are in place
Frequently Asked Questions
Does Claude have a native HubSpot integration?
Yes. HubSpot publishes an official connector for Claude, available from the connectors directory in Claude's settings. It works with HubSpot accounts across tiers and currently requires a paid Claude plan.
Can Claude update records in HubSpot, or only read them?
Both. The connector supports creating and updating contacts, companies, deals, tickets, line items, and products, plus logging calls, meetings, notes, tasks, and emails. It cannot delete records, bulk changes are limited to 10 records at a time, and changes can be routed through human approval.
Will employees see CRM data they should not?
The connector respects HubSpot permissions. Each person sees in Claude only what their own HubSpot account allows, and connector activity is attributed in HubSpot's audit log. Part of our implementation is confirming those permissions are set correctly before rollout.
What if we do not want an AI tool writing to our CRM at all?
Then we keep it read-only. You can limit what the connector is used for, require approval on every write, or skip the live connection entirely and load curated HubSpot exports into Claude as reference material. The Implementation Plan lays out which option fits your risk tolerance.
How do we get started?
Start with the Implementation Plan. We map which HubSpot data matters, which workflows to connect first, who gets access, and what stays behind human approval. Then we set up the connection, test it with one team, and expand from there.
Connect HubSpot to Claude the right way
The implementation plan identifies which connections are practical, which permissions they need, and which should remain separate.