Using Claude with HubSpot: what it builds, and what it can’t decide

Claude can build most of a HubSpot setup for you: pipelines, properties, views, reports and workflows. What it can’t do is decide what the setup should be. That part is still yours, or ours.

We’re ProfitPad, a HubSpot partner. For the past month, nearly every client build we’ve shipped was done by Claude working inside the client’s portal, from instructions we wrote. It saves us a lot of time: nobody on our team builds by hand anymore. Here’s how we connect it, what it handles, and where it still needs a person.

How to connect Claude to HubSpot

There are three ways in. They reach the same portal, but they don’t do the same job.

• HubSpot connector. In Claude, open Settings, then Connectors, find HubSpot and sign in. A Super Admin approves it first. This is HubSpot’s official MCP server, set up for you.
• Your own MCP connector. In HubSpot, go to Development, then MCP Connectors, and create one. Same server, set up by hand. Only worth it for AI tools other than Claude.
• Claude in Chrome. Install the extension and Claude works in the HubSpot screens you already use, signed in as you.

We build through Chrome. It sees what a person sees, so it can set up views, boards and reports that the connector doesn’t cover. It’s also limited the same way a person is: on a seat that can’t save views, Claude can’t either.

Connector or browser?

Use the connector to read and analyze. Use the browser to build.

The connector is safer and more predictable. The browser does the work the connector can’t reach, which is most of a real build. That’s also why the browser needs a tighter brief and a review before anyone uses what it built.

Sources: HubSpot connector for Claude, HubSpot MCP server, Using Claude in Chrome safely.

What Claude can and can’t do in HubSpot

Claude does the clicking well. It doesn’t know your business unless you tell it.

It can:

• Build pipelines and stages, properties, record views, reports and workflows, from a clear brief.
• Read and analyze your data: stage counts, empty fields, duplicates, deals stuck in a stage.
• Create and update records and activities.

It can’t, or won’t on its own:

• Delete records through the connector. HubSpot’s MCP creates and updates only.
• Get past your pipeline rules. Required fields and stage rules still apply.
• Check every property before it builds. Claude works from what you point it at. If an existing field already does the job, it may create a second one unless you name the first.
• See sensitive data. With Sensitive Data turned on, HubSpot blocks activity and conversation data from the connector.
• Decide what your stages, fields or reports should be.

A wrong stage built fast is still a wrong stage.

The brief is the work

Claude builds what you describe. A vague brief gets a plausible build that doesn’t fit how your team sells. So the time you used to spend clicking, spend on the brief.

What we put in every brief:

1. The portal. Name the account. Claude may be signed in to a different one.
2. The outcome in the rep’s words. “A rep opens a deal and sees the next step without scrolling,” not “improve the deal view.”
3. The exact fields. List the properties to use by name. Tell Claude to check for an existing property before it creates one.
4. What not to touch. Live workflows, other teams’ pipelines, anything another tool writes to.
5. How to check it. “Open three real deals and confirm the card shows the right stage.”

A brief we’d actually send:

In the Northwind portal, build a deal pipeline called New Business with five stages: Discovery, Proposal sent, Negotiation, Won, Lost. Use the existing Lead Source property; check for it before creating anything. Make Closed Lost Reason required on Lost. Build a deal view for reps with Amount, Close date and Next step. Don’t touch the Renewals pipeline or any live workflow. When you’re done, open three test deals and confirm each one shows a next step.

Then review what it built before anyone uses it.

Claude or Breeze for a data audit?

Use both. Breeze is better at coverage inside the portal: tasks, lifecycle stages, missing owners. Claude is better when the answer needs context HubSpot doesn’t hold, like proposals and invoices, and it’s the one that runs our free HubSpot audit, with a person reviewing every finding.

We tested them side by side on our own portal →

What to keep behind approval

Let Claude read freely. Make it ask before it writes.

Our rule for clients: in Claude’s settings for the HubSpot connector, set write tools to Needs Approval. HubSpot recommends the same. Claude can be set to always allow. Don’t.

Three things always get a person’s yes first:

• Changes to a pipeline reps are working in today.
• Bulk updates to records.
• Anything a live workflow or another tool also writes to.

In the browser, Claude can delete anything your seat can, and its changes log under your name. Give it the narrowest seat that can do the job, and never point it at a portal with patient data.

Four jobs worth giving Claude in HubSpot

Every client build now runs the same way: we write the brief, Claude builds in the client’s portal, and a person reviews it before the team uses it. No manual building. These are the jobs we point it at.

1. Score customers for churn and upsell. Claude helps work out what a healthy customer looks like from the data you already hold, then builds the score and the properties behind it. We built customer risk scoring this way for a returning client.
2. Catch missed follow-ups and tell the rep why. Each night, find the deals and contacts where follow-up slipped, create a task for the owner, and show the context on the record: last touch, what was promised, the next action and a suggested message. We’ve built this in our demo portal. In production it runs in n8n calling Claude, and Claude writes only to its own fields, so nothing it writes collides with a rep’s edits. The card on the record is a custom app card, which needs a HubSpot Enterprise subscription.
3. Audit the portal every week. Run the same checklist on a schedule and get a short report of what changed: new duplicates, deals stuck in a stage, fields nobody fills in. A person decides what to fix.
4. Prep the rep’s day. A morning summary of today’s meetings and calls, with the last conversation, open deals and anything promised for each one. We run this for our own team.

What we don’t hand Claude: lead routing. Who gets a lead should follow a rule your team can read, like a territory sheet. Claude builds the routing, it doesn’t make the call.

When to hand off to n8n

Claude can run on a schedule, which covers checks like a weekly audit. It can’t react the moment a record changes, and it isn’t built to move data between systems every hour without fail.

That’s where we use n8n. Claude helps design and write the automation. n8n runs it on a schedule, on a server, with logs when something fails. We run it for ERP syncs and for jobs too big for HubSpot’s own automation, like a nightly attribution run across more than 30,000 deals.

A simple test: if it reports to a person, schedule Claude. If it moves data or reacts to a change, use n8n.

Want to see what Claude finds in your portal? We run the audit and a person reviews every finding. You get the list of what’s wrong with the records behind each item, the quick wins fixed free, and a scoped plan for anything bigger. Request your free HubSpot audit →

FAQ

Can Claude set up HubSpot for me?

Yes, most of it. Claude can build pipelines, properties, views, reports and workflows from a clear brief, through the HubSpot connector or your browser. It can’t decide what your stages, fields and reports should be. A fast build of the wrong process is still the wrong process, so the brief needs someone who knows how your team sells.

Can Claude build HubSpot workflows?

Yes, through your browser. Claude in Chrome works in the HubSpot screens as you, so it can build workflows, views and dashboards from a clear brief. The HubSpot connector can’t: for workflows, it drafts the triggers and actions for you to build. Review every workflow before you turn it on.

Can Claude delete records in HubSpot?

Not through the HubSpot connector. It creates and updates records, properties and pipelines, but it doesn’t support deletes. It also respects your required fields and pipeline stage rules. Through a browser, Claude can do whatever your seat can, so keep deletes behind a person’s approval.

Is it safe to connect Claude to our HubSpot?

Yes, if writes need approval. Claude acts with your own HubSpot permissions and connects to one portal at a time. Set the connector’s write tools to Needs Approval so Claude asks before it creates or updates anything. If your account has Sensitive Data turned on, HubSpot blocks engagement data from Claude.

Can Claude audit our HubSpot portal automatically?

Yes. Set Claude to run the same audit every week and report what changed: new duplicates, deals stuck in a stage, fields nobody fills in. With write approval on, the audit changes nothing in your portal. A person still decides what to fix, because the report shows what changed and someone has to decide why.

Should we use Claude or Breeze to audit our HubSpot data?

Use both. On our own portal, Breeze was better at coverage inside HubSpot: overdue tasks, lifecycle stages, missing owners. Claude was better when the answer needed context HubSpot doesn’t hold, like proposals and invoices. Both found the same top problem, a pipeline that wasn’t in the CRM. Neither can fix missing records.

Does this work with ChatGPT or other AI tools?

HubSpot’s MCP server works with any AI tool that supports MCP, including ChatGPT and Gemini. Some tools, like website page editing, are limited to select clients. We build with Claude, so this guide covers Claude. Check HubSpot’s MCP documentation for what your tool supports before you connect it.