Build · Connectors
Connect where the knowledge already lives.
Nobody wants to re-type their company's documentation into a chat box. A connector reaches into the place that knowledge already lives and keeps reading it, rather than asking someone to copy it in once and let it go stale.
What's supported today
Seven connectors, each doing one job well.
- Google Drive: including subfolders, kept in sync as files change
- OneDrive: direct link, same sync behaviour as Drive
- GitHub: for teams whose documentation lives as code
- Slack: read as knowledge, or as a live signal an agent can act on
- Gmail: signal mode polls for unread action items
- HubSpot: your CRM (customer relationship management) record becomes something an agent can reference
- Google Search Console: top queries, top pages and performance become knowledge
What happens to a document once it's connected is the Knowledge Hub.
FAQ
Teams connecting their tools are asking
If a Company connects Google Drive, does every Agent under it have to connect its own?
No. A connection made at the Company level is inherited by every Team and Agent below it. A Team or Agent can still add its own source alongside the inherited one if it needs something narrower.
Which connectors are read-only versus read-write?
Most are read-only knowledge sources. Google Sheets is the exception. A pipeline step can write a row back to a connected sheet, not just read from it.
Do you support connectors beyond this list?
This is the current list. Tell us what you need and it goes on the roadmap. Connectors are one of the parts of the platform we extend most often.
Point an agent at where the knowledge already lives.
Twenty minutes with the founder. No slides. The real product.
