On this page
What HubSpot supports natively
Breeze is HubSpot’s AI layer. For admins, three parts matter (HubSpot articles updated September and October 2026):
| Breeze feature | What it does | Plan |
|---|---|---|
| Breeze Assistant | Chat in HubSpot’s top navigation: generates content, summarizes records, prepares meetings, completes tasks such as creating a deal or adding a note | All products and plans; admins turn it on in AI settings |
| Breeze Assistant in the workflow builder | Adds triggers and actions, configures workflow settings, generates custom code actions | Professional or Enterprise; Workflows permission |
| Agents in Agent Hub | Prebuilt agents such as the Data agent, Prospecting agent, Customer agent and Deal progression | Varies; some need Professional or Enterprise and HubSpot Credits |
Breeze Assistant acts within each user’s permissions, and content generation is limited to 100 requests per account in a rolling one-minute window.
Breeze vs Claude and ChatGPT, task by task
| Admin task | Breeze | Claude (HubSpot connector) | ChatGPT (HubSpot app) |
|---|---|---|---|
| Build or edit a workflow | Yes, in the builder | No | No |
| Create custom properties | Yes, through the Data agent | Yes (create, not edit) | Yes (create, not edit) |
| Create or edit pipelines | Not documented | Yes | Yes |
| Create or update segments (lists) | Not documented | Yes | Yes |
| Create and update CRM records | Create (e.g. a deal or a note) | Yes, 10 at a time | Yes, 10 at a time |
| Long-form analysis and research | On HubSpot data | Yes | Yes, including deep research |
| Write specs and documentation | Yes | Yes | Yes |
| Delete anything | Not documented | Not documented | No |
“Not documented” means HubSpot’s article doesn’t mention it, not that it’s impossible. Test in a sandbox. The HubSpot AI capability matrix compares the same routes asset by asset.
How to choose for HubSpot admin work
- Inside one workflow: Breeze. It works on the real canvas with the real properties, which removes the ID-guessing that external tools get wrong.
- Designing a data model or a process: Claude or ChatGPT to draft and challenge it, then build through a reviewed route. See whether to trust Claude with your architecture.
- Fields and pipelines in bulk: both connectors can create them and update pipelines, but neither can edit a property afterwards, so get the spec right first. Set their write tools to Needs Approval so every change is shown before it runs.
- Anything across portals or many connected assets: none of the three tracks dependencies between assets for you.
- Building new setup (fields, pipelines, lists and the workflows that use them): we recommend Jetstack AI Projects, which plans the build, orders it by dependency and asks for approval before anything is deployed. See how it compares with Breeze, Claude and the HubSpot MCP and ChatGPT.
The wider comparison, including MCP servers, is in which AI tools can change your portal setup.
Where Jetstack AI fits
Use Jetstack’s Projects when the job is building setup rather than working inside one workflow. You describe the properties, pipelines, lists, forms and workflows in a brief; Jetty, the Projects assistant, turns it into a plan you approve, generates the assets, and deploys them after a separate approval. The receipt confirms each asset by reading it back from HubSpot, and workflows are created switched off. It’s an implementation workflow rather than an assistant, and it works alongside Breeze. Projects is currently in limited release; see what Projects can build.
Sources
- Use Breeze Assistant (HubSpot Knowledge Base)
- Build workflows using Breeze Assistant in Agent Hub (HubSpot Knowledge Base)
- Set up and use the HubSpot connector for Claude (HubSpot Knowledge Base)
- Connect your HubSpot account to ChatGPT (HubSpot Knowledge Base)
- Create and edit properties (HubSpot Knowledge Base)
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