Import connectors
Connector imports are how external provider content becomes useful to the API without adding provider-specific fields to every route.
1: Connect a provider
Provider authorization is a user-account workflow, not a generation call. The user signs in, opens the integrations settings page, and connects Google Drive or Notion there. That surface is also where health, reconnect, and disconnect actions live.
2: Choose items
The connector layer exists so the user can be explicit about what should become learning context. In practice that means selecting the page, document, or file that should feed the next generation call instead of handing Vidbyte unrestricted workspace access at the route boundary.
Google Drive is designed around Drive resources such as docs and files. Notion is designed around workspace pages today.
3: Use as context
Vidbyte does not maintain a second, provider-specific parser path for each route family. The integrations system normalizes the selected provider content into the same content shapes the API already expects, which means the actual generation call still reasons about `context` instead of about provider-specific OAuth state.
Request example
Context pattern
{
"prompt": "Generate a roadmap from the imported source material",
"context": [
{ "type": "text", "label": "imported_connector_content", "text": "<normalized imported content>" }
]
}