What This Update Actually Is
HubSpot is removing eight Breeze Assistant connectors from the Marketplace. These aren't obscure tools; some are used daily by product, support, and ops teams.
The eight connectors being removed are:
- Smartsheet
- GitBook
- Azure DevOps
- Guru
- ReadMe
- Productboard
- Helpjuice
- Document360
New installs are already blocked. Existing connections stop working automatically on September 26, 2025. This affects all hubs and all tiers.
Why HubSpot Shipped This
These connectors were built on an older architecture that HubSpot is no longer maintaining. Keeping them running creates reliability risks for everyone, including the connectors that are actually performing well inside Breeze Assistant.
This is a deliberate trade-off. HubSpot is choosing a smaller, more reliable connector catalog over a larger, patchwork one. That's a reasonable call, but it does put the burden on your team to act before the deadline.
The internal frustration here is real. Humans who built their Breeze Assistant workflows around one of these tools now have to rebuild or reroute. If you've trained your team to use Breeze with a connected knowledge base like Guru or Document360, that workflow breaks on September 26 without any warning inside the product.
How to Use It Step by Step
You don't have to wait for September 26. The best move is to handle this now so nothing breaks mid-quarter.
- Go to Settings > Integrations > Connected Apps in your portal.
- Scan the list for any of the eight affected connectors.
- Disconnect each affected connector manually before September 26.
- Check if a replacement connector exists for your tool in the same Connected Apps page. HubSpot may have a newer version built on the updated architecture.
- If no replacement exists, document which Breeze Assistant workflows relied on that connector so your team knows what changed.
- Notify any team member who uses Breeze Assistant for knowledge lookups or cross-tool context so they're not caught off guard.
If you don't disconnect before the deadline, HubSpot will remove the connections automatically. There's no graceful hand-off. The connector just stops working.
What It Touches in Your HubSpot Strategy
This change is narrow in scope but wide in impact for any team that built Breeze Assistant into their daily workflow. Here's where to look.
Breeze Assistant context quality depends on what it's connected to. If your Breeze setup pulled answers from a connected knowledge base like Guru, Helpjuice, or Document360, those answers stop loading after September 26. Breeze doesn't fail gracefully here; it just loses the context.
Cross-functional teams are the most exposed. Product teams using Productboard or ReadMe integrations and engineering teams using Azure DevOps or GitBook connections have likely tied those tools into their HubSpot context layer. That's the layer that lets Breeze give relevant answers based on live data from those platforms.
Key Takeaway
If any of your Breeze Assistant prompts rely on context from a connected third-party tool, audit those prompts now. Without the connector, Breeze will answer from HubSpot data only, which may produce incomplete or misleading results for your team.
Project management workflows are also at risk. Smartsheet is widely used for operational planning, and if your team set up Breeze to pull project data or status updates from Smartsheet, that integration is gone.
If you're still getting up to speed on what Breeze Assistant actually does and how connectors fit into its architecture, read Breeze Has Hands Now: What HubSpot's Breeze Assistant Can Really Do. And if you want to see real prompt examples before you rebuild any workflows, HubSpot Breeze Assistant Prompts, Demoed Live by the Team That Built and Teaches It is the most practical starting point we've seen.
Key Takeaway
This removal also signals a broader HubSpot direction: Breeze connectors will be held to a higher reliability standard going forward. Connectors that don't meet that bar will be cut, not patched. When you reconnect or rebuild, prioritize connectors that HubSpot actively maintains on the updated architecture.
On the positive side, HubSpot is clearly investing in the Breeze ecosystem in other ways. If you're seeing Breeze's context capabilities improve elsewhere in your portal, that's part of the same shift. One recent example is Revenue Context for Contracts in Breeze, which shows the direction HubSpot is heading with native, well-maintained AI context.
Who Should Care Most
This update is relevant across all hubs and tiers, but the urgency is higher for specific roles.
- HubSpot admins and RevOps leads: check Connected Apps now and document anything that's at risk before the September 26 cutoff.
- Product and engineering teams: if your team uses GitBook, ReadMe, Azure DevOps, or Productboard alongside HubSpot, your Breeze context layer is about to change. Identify the gap before it affects a customer-facing workflow.
- Customer support and knowledge management teams: Guru, Helpjuice, and Document360 are common knowledge base tools for support orgs. If Breeze was surfacing answers from those sources, that stops working at the deadline.
- Operations managers using Smartsheet: any Breeze workflows pulling project or resource data from Smartsheet need to be rerouted or replaced.
Company size doesn't change the risk here. A two-person ops team that built a Breeze workflow around Document360 is just as exposed as an enterprise that runs Guru across 200 humans in their support org.
George's Take
I've audited a lot of portals, and connector sprawl is one of the most overlooked risks in any HubSpot setup. Humans connect tools, workflows get built around those connections, and then nobody checks whether those connections still work, still matter, or are even still supported. This removal is a forcing function. It's uncomfortable, but it's a good moment to be intentional about what you actually want Breeze to know and why. Don't just reconnect the same tools out of habit. Ask whether those connections were actually improving your Breeze context or just adding noise.
“Connector sprawl is one of the most overlooked risks in any HubSpot setup. This removal is a forcing function. Use it to be intentional about what you want Breeze to know and why.”
If this kind of deprecation pattern concerns you, it's worth knowing this isn't isolated. HubSpot is actively cleaning up older architecture across the board. The Pipelines API V1 deprecation is another example of the same direction. Getting ahead of these changes is a RevOps discipline, not a one-time fix.
If your portal has any of the affected connectors, or if you're not sure what's connected to your Breeze setup at all, let's take a look together. Book a strategy call with the Sidekick team and we'll audit your Connected Apps, identify the gaps, and help you rebuild on connectors that are actually going to hold up.
Frequently Asked Questions
Which Breeze Assistant connectors are being removed by HubSpot?
HubSpot is removing eight Breeze Assistant connectors: Smartsheet, GitBook, Azure DevOps, Guru, ReadMe, Productboard, Helpjuice, and Document360. New installs are already blocked, and existing connections will be automatically removed on September 26, 2025. This affects all HubSpot hubs and tiers.
What happens if I don't disconnect the affected Breeze connectors before September 26, 2025?
HubSpot will automatically remove any remaining connections to the eight affected connectors on September 26, 2025. There's no grace period after that date. Any Breeze Assistant workflows that relied on those connectors for context will stop receiving that data, which can break prompts and responses your team depends on.
Why is HubSpot removing these Breeze Assistant connectors?
These connectors were built on an older architecture that HubSpot is no longer maintaining. Keeping them active creates reliability risks. HubSpot is removing them to focus investment on connectors that perform reliably within the current Breeze Assistant architecture.
How do I find out if my portal uses one of the affected Breeze connectors?
Go to Settings > Integrations > Connected Apps inside your HubSpot portal. Scan the list for Smartsheet, GitBook, Azure DevOps, Guru, ReadMe, Productboard, Helpjuice, or Document360. If any appear, disconnect them before September 26, 2025, and check whether a replacement connector is available on the same page.
Are there replacement connectors available for the tools being removed?
HubSpot says you can check for replacement connectors from the same Connected Apps settings page. Not all eight tools have confirmed replacements. If a replacement exists, it will be built on the updated architecture. If one doesn't exist yet, you'll need to consider alternative tools or workflows for your Breeze Assistant setup.
Does this change affect all HubSpot hubs and pricing tiers?
Yes. The removal of these eight Breeze Assistant connectors affects all HubSpot hubs and all pricing tiers, from Free to Enterprise. Any portal that has one of the affected connectors installed needs to take action before September 26, 2025, regardless of their subscription level.
