HubSpot integration guide
How to keep HubSpot up to date
Articles in your HubSpot help center go wrong when a feature in your product changes and nobody tells the person who owns the article.
Keeping help centers accurate at
The short answer
- What HubSpot offers
- Your HubSpot knowledge base has features like the Analyze tab's article feedback, Coaching opportunities in the customer agent, and a beta knowledge base agent that suggests edits to existing articles.
- Where it stops
- The signals all arrive after the fact, as a rating or an unanswered customer question, and none of them reads your code changes.
- Where Solo fits
- Solo compares your code changes with your articles, flags the ones a change made wrong, and drafts fixes that a person approves before they reach HubSpot.
On this pageShort answer
Why it matters
Why an accurate knowledge base matters
A feature in your product changes on Tuesday, and on Friday the article for it still shows the old setting. Readers follow the old steps, the customer agent repeats them, and public articles quote the old setting in search.
Customers solve problems without a ticket
A current article ends the visit. A wrong one sends the reader to chat or your support team, and an unhelpful rating on the article is often the first sign.
Your customer agent resolves more conversations
The HubSpot customer agent answers from the content sources you give it, including knowledge base articles, and it re-syncs on its own when a synced article is updated. A stale article becomes a confident wrong answer, because the agent decides on a handoff from its own confidence in the source.
Public articles show up correctly in search
Search engines and AI answer engines quote public articles, so a wrong one gives the answer before anyone reaches your team. Fixing the original later doesn't change the copies already quoted.
Built-in tools
Maintaining HubSpot knowledge base articles with built-in tools
HubSpot has real signals for this: article feedback and search reports in the Analyze tab, Coaching opportunities in the customer agent, and a beta knowledge base agent that suggests edits. All of them react to a customer, a ticket or a conversation, and none can see that your product changed.
| Stage | HubSpot's features | Missing features |
|---|---|---|
| 01Know upcoming changes | HubSpot has no feature for this stage, so notice of a change to your product has to come from a product manager or a developer. | Nothing warns the article owner before a feature in your product changes, because HubSpot doesn't see your code, feature flags or launch plans. |
| 02Identify outdated articles | The Analyze tab shows helpful and unhelpful ratings with a reason such as Unclear or Missing information, plus search terms with no results, and the customer agent's Coaching opportunities flag knowledge gaps and conflicting sources. | All of these arrive after a reader or the customer agent has hit the wrong article, and none says which article a change to your product made wrong. |
| 03Draft updated copy | The knowledge base agent, in beta, reviews existing articles and suggests edits where content may be unclear, outdated or incomplete, and Breeze Assistant can rewrite, expand or shorten text you highlight in the editor. | The knowledge base agent works from closed tickets and existing wording, and Breeze Assistant works from the text you highlight, so neither sees what your product now does. |
| 04Collaborate on updates | Editing needs a Service Hub seat and the Knowledge base articles permission, and the knowledge base agent's suggested edits can be accepted, dismissed or saved as a draft for a teammate to finish. | Permissions control who can edit, not which articles a change to your product made wrong, so reviewers still have to work out what a change touched. |
| 05Publish changes | Publish or Update pushes an article live, Scheduling options can set a publish, update or unpublish for a date and time, and the customer agent re-syncs on its own when a synced article changes. | Scheduling runs on a fixed date, not when a feature flag turns on, so an article goes live on someone's calendar rather than when your product changes. |
With Solo
Knowledge base management with Solo on top of HubSpot
HubSpot can't see your codebase, so it can't tell which knowledge base articles a change to your product made wrong. Solo connects to your HubSpot articles, compares them with your code changes, flags what a change made wrong and drafts a fix for each one. A person on your team reviews every fix before anything is written to HubSpot.
What Solo adds to HubSpot's built-in tools
| Stage | HubSpot without Solo | HubSpot with Solo |
|---|---|---|
| 01Know upcoming changes | HubSpot has no feature for this stage, so notice of a change to your product has to come from a product manager or a developer. | Solo reads recent code changes from your connected repositories and turns each one into a short description of your product change, so the owner hears without being told. |
| 02Identify outdated articles | The Analyze tab shows helpful and unhelpful ratings with a reason such as Unclear or Missing information, plus search terms with no results, and the customer agent's Coaching opportunities flag knowledge gaps and conflicting sources. | Solo indexes your HubSpot articles and searches them for text your code changes contradict, showing the affected text, the reason and the change behind it before a reader rates the article. |
| 03Draft updated copy | The knowledge base agent, in beta, reviews existing articles and suggests edits where content may be unclear, outdated or incomplete, and Breeze Assistant can rewrite, expand or shorten text you highlight in the editor. | Solo drafts replacement text for the sentences a change to your product made wrong and can flag an image that may be outdated, so a writer starts from a draft. |
| 04Collaborate on updates | Editing needs a Service Hub seat and the Knowledge base articles permission, and the knowledge base agent's suggested edits can be accepted, dismissed or saved as a draft for a teammate to finish. | Reviewers see the old and proposed text next to your code change behind it, and can edit, accept, add to a draft, reject, snooze or mark each suggestion resolved elsewhere. |
| 05Publish changes | Publish or Update pushes an article live, Scheduling options can set a publish, update or unpublish for a date and time, and the customer agent re-syncs on its own when a synced article changes. | Accept writes the approved update to the HubSpot article, while Add to Draft keeps it in Solo until a person publishes it. A suggestion can be snoozed until a feature flag changes if the update should wait. |
Questions
Common questions about HubSpot articles and the customer agent
The questions HubSpot teams ask most often before connecting Solo to their knowledge base.
How do I know which HubSpot articles are outdated?
HubSpot gives you signals, not answers. The Analyze tab shows helpful and unhelpful ratings and search terms with no results, and Coaching opportunities lists conversations where the customer agent hit a knowledge gap or conflicting sources. None of them can tell you that a setting was renamed last week, so that comparison has to start from your product itself.
What does HubSpot knowledge base AI read from my articles?
The HubSpot customer agent answers from the content sources you give it, and knowledge base articles are one option next to website pages, uploaded files and public URLs. Articles re-sync when you update them, while other sources re-sync weekly. The knowledge base agent is a separate beta feature that reviews your articles and suggests edits.
Do translated HubSpot articles need the same fix?
Yes. HubSpot links language variants to a primary article through language groups, but each variant has its own text. A fix in one language needs the same fix in the others.
Does Solo replace HubSpot?
No. Your articles, categories and customer agent stay in HubSpot, and readers keep the same URLs. Solo connects to your knowledge base, works out which articles a change to your code made wrong and drafts the fix. A person on your team approves each change before it is written to the article.
Will Solo publish to your articles without review?
No. Solo flags the articles a change to your product made wrong and drafts the text, and a person reviews each suggestion before anything changes. Accept writes the approved update to the HubSpot article, while Add to Draft keeps it in Solo until you publish it.
How does Solo know that a feature in your product changed?
Solo examines recent changes in your connected code repositories and turns them into short descriptions of your product changes. It then looks for article content those changes contradict. It can also show a feature flag and its rollout status on a review item when that status is available, for example from LaunchDarkly.
Related guides
Also works with
Solo works with the help center platform you already run, and each guide covers what is specific to that platform.
Further reading on help center drift
Why Help Center Content Goes Stale After a Product Launch
Why help center content goes stale after a product launch, what breaks behind the scenes, and how support teams can catch the drift before customers do.
6 min read
Self-Updating Help Center: How It Actually Works
A self-updating help center catches product changes before customers do. Here's what "automatic" really means, and what still needs a human.
4 min read
Best Tools to Build an AI Knowledge Base (2026)
A practical breakdown of AI knowledge base tools for support teams, what actually separates them, and the accuracy problem most vendors don't mention.
4 min read
See which HubSpot articles need a fix
A demo runs Solo against your own HubSpot knowledge base content and codebase, so the articles it flags are yours.