Connect a provider, choose items, normalize them, then use them in generation requests
Bring connector-selected content into the context layer
Connector imports are how third-party content becomes useful to the public API without expanding the live request DTOs. The integrations system owns provider connection and artifact discovery. The API keeps using the existing `context` contract after that material has been normalized into Vidbyte-readable content.
Step 1
Connect provider
Authorize Google Drive or Notion from the integrations settings surface.
Step 2
Select artifacts
Choose the external docs, files, or pages you want Vidbyte to read.
Step 3
Use as context
Feed the imported material through the same context adapter used by the live routes.
Step 1
Connect the provider in settings before you try to use its content
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.
Step 2
Choose the exact external items you want Vidbyte to read
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.
Step 3
Imported content is normalized before it reaches the public route contract
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 pattern
Use imported material through context
{
"prompt": "Generate a roadmap from the imported source material",
"context": [
{ "type": "text", "label": "imported_connector_content", "text": "<normalized imported content>" }
]
}