On this page
What HubSpot supports natively
HubSpot’s connector for Claude lets Claude read your portal and make some changes. What it can build is narrower than what an architecture needs (as of October 2026):
| Architecture piece | Through HubSpot’s Claude connector |
|---|---|
| Custom properties | Read and create. Not update |
| Pipelines and stages | Read, create and update |
| Custom object records | Read, create and update (records, not new object definitions) |
| Segments (lists) | Read, create and update |
| Workflows | Not supported. Claude drafts, you build in HubSpot |
| Delete anything | Not supported per HubSpot’s article. In our testing (October 2026), the connector’s segment tool offered delete and restore for lists |
The connector also creates or updates at most 10 records at a time, and HubSpot notes that association label validations aren’t applied to records it writes. So Claude can lay down fields and pipelines, but the automation layer, the part that breaks quietly, stays with you.
Where Claude helps and where it’s confidently wrong
Good at: turning a messy brief into a clean property list, proposing stage definitions, spotting fields you forgot, explaining how an existing workflow behaves, and writing the documentation nobody else will.
Risky at:
- Inventing what it can’t see. If it can’t read a dependency, it may assume a property or option value exists.
- Plausible but wrong data model calls. Custom object versus property versus association label is a business decision. Claude picks one with confidence.
- Lifecycle logic. Rules that each look fine can fight each other once three workflows set the same property.
- Drift from the real portal. A design written from a prompt doesn’t know about the 40 properties someone created in 2021.
These errors surface months later in reporting, which is the Reddit thread’s real worry.
How to use Claude to build HubSpot architecture safely
- Read before you write. Have Claude inventory existing properties, pipelines and lists first, and design around what’s there.
- Ask for a spec, not changes. Internal names, types, option values, stage rules and which workflows set each field.
- Review the decisions, not the prose. Check every object choice, every required field and every property more than one workflow writes.
- Build in a test portal first. A sandbox or a free developer test account.
- Read it back. Compare what HubSpot saved with the spec. A summary saying “done” isn’t evidence.
- Set write tools to Needs Approval. HubSpot recommends it in the connector’s tool settings in Claude. Claude may show proposed changes and ask before writing, but with Always allow edits can happen without asking, so don’t rely on a prompt you haven’t required.
See is it safe to give Claude write access to HubSpot for the permission side. To run these steps without building the process yourself, we recommend Jetstack AI Projects; see how it compares with Claude and the HubSpot MCP.
Where Jetstack AI fits
Jetstack’s Projects puts the review steps above into the product. You give it the brief Claude would have drafted from: field lists, pipeline stages, workflow descriptions, call notes. Jetty, the Projects assistant, reads the portal first, writes a plan you approve before anything is generated, builds properties before the workflows that use them, and waits for a separate approval before deployment. The receipt shows what HubSpot accepted by reading each asset back. It builds properties, pipelines, lists, forms and workflows (created switched off), among other types, and it’s currently in limited release; see what Projects can build. If you copy a tested setup in with Portal reuse instead, you can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment.
Sources
- Set up and use the HubSpot connector for Claude (HubSpot Knowledge Base)
- Integrate with the remote HubSpot MCP server (HubSpot Developers)
- HubSpot account types (HubSpot Developers)
- What Jetty can build (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
AI, Claude & MCP
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects