What This Update Actually Is
HubSpot shipped a private beta that puts Breeze Assistant inside Anthropic's Claude AI interface. It's not a chatbot plugin or a separate tab. Breeze becomes a callable tool inside your Claude conversation.
When you include phrases like "Ask Breeze to..." or "Have Breeze..." in your Claude prompt, Claude routes that request to the Breeze Assistant via the ask_breeze tool. Breeze does the work in your HubSpot portal and returns the answer inside the same conversation thread. Follow-up questions carry forward the context already established, so you don't have to re-explain your situation every time you ask something new.
The September 28, 2026 update also added something important for ops and security teams: every mutation Breeze performs from Claude is now captured in HubSpot's centralized audit logs and attributed to Breeze Assistant. That means you have a full paper trail of any record Breeze reads or updates.
Access is limited to super admins during this preliminary private beta. Permissions and governance features are still being built out.
Why HubSpot Shipped This
Here's a pattern we see constantly across HubSpot portals: the data is in HubSpot, the analysis is happening somewhere else, and the two rarely meet at the right time. A sales manager opens Claude to think through a forecast, then switches to HubSpot to pull the actual pipeline numbers, then goes back to Claude to make sense of them. That context-switching is where insight gets lost.
HubSpot's pitch here is direct: Breeze carries two decades of go-to-market intelligence built across hundreds of thousands of businesses. It doesn't just retrieve your data; it knows what normal looks like for companies at your stage, which signals actually predict outcomes, and what's worked historically. Claude now has a GTM consultant it can call on, not just a database lookup.
The internal frustration this solves isn't just switching tabs. It's the feeling that your AI tools and your CRM exist in separate universes, and you're the one bridging them manually every time you need an answer.
How to Use It Step by Step
Note: This is a private beta. You need to be a HubSpot super admin and enrolled in the beta before these steps apply.
- Confirm your beta access. Only super admins can enroll during the preliminary phase. Check with your HubSpot account team or watch for an enrollment prompt inside your portal.
- Open a conversation in Claude. You don't need a special Claude plan beyond what gives you tool access. The Breeze integration surfaces through the ask_breeze tool once the connection is established.
- Write a prompt that explicitly routes to Breeze. Use trigger phrases like "Ask Breeze to..." or "Have Breeze...". This is how Claude knows to call the Breeze tool rather than answering from its own training data.
- Start with a high-value use case. HubSpot recommends three strong starting points: deal risk signals for sales, campaign pipeline influence for marketing, and account engagement health for CS and service teams.
- Ask follow-up questions without re-explaining context. Breeze carries the conversation thread. You can go from "which deals show risk signals" to "what do those deals have in common" in the same thread.
- Submit feedback using the submit_feedback tool inside Claude. HubSpot's team wants specifics: what you were trying to do and the exact prompt you used. That's the most useful signal for them right now.
- Verify audit entries. After Breeze updates or reads records, check HubSpot's centralized audit logs to confirm the actions are attributed to Breeze Assistant. This is your governance safety net during the beta.
What It Touches in Your HubSpot Strategy
This update isn't a feature in a single hub. It's a new interface layer that sits above the data across your whole portal. Here's where the ripple lands.
Sales Hub and CRM Records. Breeze can read and update deal records, contact records, and company records from Claude. That means a sales leader can ask Breeze to flag stalled deals based on historical close signals, review the output in Claude, and have Breeze update properties or notes without opening HubSpot once. For teams that have already explored what Breeze can do on tasks, this extends that workflow into a conversational AI interface.
If your team has been using Breeze Assistant on tasks inside HubSpot, this Claude integration is the logical next step. Same intelligence, broader access point.
Key Takeaway
Every record mutation Breeze performs from Claude is logged in HubSpot's centralized audit logs and attributed to Breeze Assistant. This is non-negotiable for RevOps and IT governance teams evaluating whether to greenlight broader beta use.
Marketing Hub and Campaign Attribution. Marketing ops humans can ask Breeze which campaigns drove the most pipeline influence in a past quarter and surface that data directly in Claude for analysis. This is meaningful because attribution questions usually require toggling between reports, filtering by campaign type, and manually cross-referencing contact timelines. Breeze collapses that into a single prompt.
Attribution data is only valuable when both sales and marketing trust the same numbers. If your team is still sorting out which attribution model holds up under scrutiny, our article on building revenue attribution your sales team actually believes gives the strategic foundation before you layer AI queries on top.
Service Hub and Account Health. CS and service humans can ask Breeze to surface accounts showing early disengagement signals. This mirrors what HubSpot's health score tooling does inside the portal, but now it's queryable in natural language from Claude, with Breeze interpreting the pattern rather than just returning a number.
Key Takeaway
The scope of this beta covers HubSpot records, marketing campaigns and emails, customer conversations, and company intelligence. All Breeze actions run within your existing HubSpot permissions, so no data leaves its permission boundary.
Operations and Governance. The audit log attribution is the ops story here. Before this update, AI-initiated changes to CRM records were difficult to trace. Now every Breeze action from Claude has a clear owner in the log. RevOps teams should pull a sample audit check in the first week of beta use to confirm attribution is working as expected in their portal.
Who Should Care Most
This update is most immediately relevant to a specific set of roles and company profiles.
- HubSpot super admins at companies already using Claude who want to evaluate AI-to-CRM integration before it hits general availability.
- Sales operations humans who review pipeline health regularly and want faster, conversational access to deal signals without building custom reports every time.
- Marketing ops leaders who do quarterly campaign attribution reviews and want to collapse a multi-step report process into a single AI prompt.
- RevOps and IT stakeholders evaluating AI governance, since the new audit log attribution gives them the paper trail they need to feel safe greenlighting broader access.
- Customer success and service managers at mid-market companies who monitor account health signals and want to surface at-risk accounts faster than their current manual review process allows.
This isn't ready for every seat in the org yet. Governance is still in progress, and the beta scope is intentionally narrow. If you're not a super admin or you don't have Claude access already, put this on your radar for Q1 2027.
George's Take
I've watched HubSpot portals accumulate years of great data that humans almost never query because the interface gets in the way. You know the answer is in there somewhere, but building the report feels like a tax on your curiosity, so you guess instead. What this Claude integration does, even at early beta, is remove that tax. When I can ask Breeze which deals historically don't close from a conversation I'm already in, the question gets asked. That's the shift. Not that AI is smarter, but that the friction is low enough that smart humans actually use it.
“The data was always there. What was missing was a question worth asking and a fast enough way to ask it. That's what this beta is actually testing.”
The governance piece matters too. I won't encourage any team to expand AI access into their CRM without an audit trail. The fact that HubSpot added attribution to the audit logs before pushing this wider isn't a footnote, it's the responsible move. Humans who flourish with AI aren't the ones who move fastest. They're the ones who move with clarity about what's happening and why. If you want to think through the bigger picture of how AI agents fit into your workflow without handing over judgment, our piece on being the most human human in an agent-native world is worth your time.
If you're a super admin with Claude access and you want to beta test this in a way that actually moves your strategy forward, not just play with the shiny new thing, let's map it to a real use case in your portal. Book a strategy call with the Sidekick team and we'll help you set up the right prompts, review your audit log setup, and identify which pipeline or attribution question will give you the fastest signal on whether this tool earns a permanent seat at your table.
Frequently Asked Questions
What is Breeze Assistant in Claude?
Breeze Assistant in Claude is a private beta integration that lets you call HubSpot's Breeze AI from inside an Anthropic Claude conversation. Using trigger phrases like "Ask Breeze to..." you can pull pipeline data, flag deal risks, surface campaign attribution, and read or update HubSpot records without leaving Claude.
Who can access Breeze Assistant in Claude right now?
Access is limited to HubSpot super admins during the preliminary private beta. Permissions and governance features are still being built. If you're not a super admin, watch for general availability announcements later. Non-super-admin users are not eligible for enrollment at this stage.
Are changes Breeze makes from Claude tracked in HubSpot?
Yes. As of the September 28, 2026 update, every mutation Breeze performs from Claude using the ask_breeze tool is captured in HubSpot's centralized audit logs and attributed to Breeze Assistant. This gives RevOps and IT teams a clear paper trail for governance and compliance review.
What can Breeze Assistant actually do inside Claude?
During the private beta, Breeze can work with your HubSpot records, marketing campaigns and emails, customer conversations, and company intelligence. It can analyze pipeline health, surface deal risk signals, pull campaign attribution, and flag at-risk accounts, all within your existing HubSpot permissions.
How do I prompt Claude to use Breeze Assistant?
Use phrases like "Ask Breeze which open deals show risk signals" or "Have Breeze pull campaign pipeline influence for last quarter." Claude routes the request to Breeze via the ask_breeze tool automatically when it detects these trigger phrases in your prompt. Follow-up questions carry forward the conversation context.
How do I give feedback on the Breeze Assistant Claude beta?
Use the submit_feedback tool inside Claude. HubSpot's product team says the most useful feedback includes what you were trying to accomplish and the exact prompt you used. Specific, reproducible examples help them prioritize fixes and new functionality faster than general impressions.
