YouTube

Install corsair and @corsair-dev/youtube, add the YouTube plugin, and connect with OAuth. Then call methods like corsair.youtube.api.captions.list() from your app. Corsair stores tokens, and syncs data per tenant.

Yes. YouTube needs an OAuth app with scopes that match what you automate. Register the app in YouTube, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit YouTube, GitHub, Notion, Stripe, and the rest. Trigger YouTube from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for video platform for uploading, managing channels, playlists, analytics, and content metadata. Common builds include sync jobs, admin tooling, and agents that call YouTube APIs from your backend. Local DB entities let you query synced YouTube records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per YouTube API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/youtube in the open repo. When YouTube ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your YouTube data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store YouTube data on your behalf.