Connectors
You can upload documents to a knowledge base by hand, but your documents usually live somewhere that keeps changing. A connector links the knowledge base to that source, imports everything in scope, and then keeps it current on a schedule.
What you will learn
Connect once
Pick the source, authorize the account, choose the scope, which pages or folders, and how often to sync.
The first import
Everything in scope comes in and is processed into chunks, the same as documents you upload by hand.
It stays current
On each sync, changed documents are re-imported and re-chunked, and documents removed at the source are removed from the knowledge base too.
Answers reflect the source
Agents searching the knowledge base read the synced content: so an answer reflects the document as it is now, not as it was at import.
The lifecycle
The video follows one connector through its whole life: picking Notion as the source, authorizing the account, scoping which pages sync, and choosing the frequency. The first import brings everything in scope into the knowledge base as chunks. From then on the connector re-syncs on schedule: a page edited at the source is re-imported, and a page deleted at the source leaves the knowledge base.
Why it matters
Knowledge that drifts out of date is worse than no knowledge: an agent will confidently answer from a stale document. A connector makes the knowledge base track the source, so the answers your agents give reflect what your documents say now.