Connectors
Connectors let users link third-party workspaces to Vidbyte so selected external content can feed the same context layer used by the API.
What a connector is
The connector model exists so users do not have to copy and paste source material manually every time they want to generate a roadmap, quiz, exam, project, or quickhit. Instead, they connect a provider account once, choose the specific external artifacts they want Vidbyte to read, and let Vidbyte normalize that content into the same request pipeline the API already understands.
That keeps the public API contract simpler. Your application still reasons about context. The connector system handles the provider-specific authorization, resource discovery, and content import work behind the scenes.
Current connectors
Google Drive
Use Google Drive when the user wants to select Drive files, folders, or Google Docs and bring that material into Vidbyte as readable context.
Notion
Use Notion when the user wants to select workspace pages and turn those pages into normalized text that Vidbyte can use in a request.
Where users connect
Users connect providers from the integrations settings page. That keeps OAuth, reconnect flows, and provider health management out of the public request contract.