Chifty
We're looking for pilot customers for early access to Chifty.Apply now

Chifty Knowledge

HubSpot content as a knowledge source for AI

Chifty Knowledge connects HubSpot to your central knowledge base. Approved content becomes searchable and flows into answers and email drafts with cited sources – without the AI ever bypassing permissions.

How does AI search HubSpot content?

Chifty Knowledge connects HubSpot as a knowledge source: content you approve becomes part of your central knowledge base and is available in Chifty Chat and Chifty Office. The AI only uses what is approved for the asking person – permissions are checked on every request, and every answer cites its sources.

What gets connected

Over the years, HubSpot accumulates valuable knowledge about customers, processes, and answers to recurring questions. With Chifty Knowledge, you connect HubSpot as a knowledge source to your central knowledge base: the content you approve becomes findable there – alongside documents, notes, and other connected sources such as Google Drive, OneDrive, or SharePoint. You copy nothing and maintain nothing twice; the knowledge stays in HubSpot and becomes usable in Chifty.

That knowledge is used where your team already works: in Chifty Chat, employees ask questions in plain language and receive answers that cite the sources used. In Chifty Office, approved knowledge flows into email reply drafts – and every draft is reviewed and sent by you.

Permissions stay intact

Not every piece of information in HubSpot belongs in every hand. That's why Chifty follows a simple principle: the AI must not bypass permissions. You decide which content is approved for which people, roles, or teams – and the AI relies solely on those approvals in every search, answer, and draft.

The permission filter is applied directly in the search, before an answer exists – the AI itself cannot influence it. Two people can ask the same question and receive different answers, because each only sees the sources approved for them. And since every answer shows its sources, it stays traceable what it is based on.

Honest limits

  • The connection needs read access to the content you approve for Chifty – without that approval, the AI cannot use anything from HubSpot.
  • Answer quality depends on content quality: outdated or incomplete information in HubSpot does not get better through AI.
  • Chifty is a young product, and we are actively developing our connectors. What your specific use case needs is something we would rather clarify honestly in a conversation than promise across the board.

Frequently asked questions

How is data privacy handled when connecting HubSpot?
Chifty is hosted in Germany, transfers are encrypted with TLS throughout, and AI processing runs in the EU by default. You control access via role and permission management. Your content is not used to train AI models, and with Google Cloud Vertex AI and OpenAI we have contractually agreed that requests are not retained after processing. A DPA under Art. 28 GDPR is available on request.
Which Chifty product do I need for this?
Chifty Knowledge – that's where HubSpot is connected as a knowledge source and the shared knowledge base is managed. The knowledge is then used in Chifty Chat, where answers cite their sources, and in Chifty Office, where it flows into email drafts.
Can the AI read everything in HubSpot?
No. The AI relies solely on the content you have approved and respects the permissions of the person asking. The permission filter is applied directly inside the search on every request – the AI cannot bypass or influence it.
Can I search my HubSpot knowledge with AI?
Yes. Approved HubSpot content becomes part of your Chifty knowledge base and can be searched by asking questions in plain language – together with documents, notes, and other connected sources. Every answer cites the sources used, so statements can be verified directly.
Is our HubSpot data used to train AI models?
No. Your content is not used to train the AI models we use. With Google Cloud Vertex AI and OpenAI, we have additionally agreed contractually that requests are not retained after processing.

Related

Chifty KnowledgeAll integrationsSecurity