YouTube — how to connect

Uploads videos to your YouTube channel via the Data API v3 (video upload only — the YouTube API has no Community-post endpoint for text, images, polls, quizzes, or video-link posts). Add your Google OAuth client ID and secret below, then connect with OAuth. Note: unaudited API projects have all uploaded videos force-locked to private by Google regardless of the privacy setting you choose.

YouTube's connect method is OAuth via a Google Cloud project. The adapter only needs a Google OAuth client ID/secret (plus an optional default privacy setting) — no per-account paste values, since the OAuth flow itself mints the channel token.

Before you start

A Google Cloud project with the YouTube Data API v3 enabled, plus an OAuth 2.0 Client ID/Secret (Web application type) whose authorized redirect URI exactly matches this tool's callback — set as YOUTUBE_CLIENT_ID / YOUTUBE_CLIENT_SECRET.
A YouTube channel you can manage: during the Google consent screen you must sign in with the Google/brand account that owns or manages the target channel (the tool lists all channels that account can access).
The OAuth consent screen configured with the youtube.upload and youtube.force-ssl scopes, and — if the app is still in "Testing" publishing status — your Google account added as a test user, or the flow will be blocked.
A video file ready to attach: the YouTube integration is video-upload only. Community text, images, image polls, text polls, quizzes, and video-link posts are not publishable through the YouTube API.
Accept the forced-privacy caveat up front: until your Google Cloud project passes YouTube's API Services compliance audit, every uploaded video is force-locked to Private regardless of the privacy setting you choose here.

Step by step

1
Create or select a Google Cloud project
In the Google Cloud Console, create a new project (or pick an existing one) that will own the YouTube integration.
Open
2
Enable the YouTube Data API v3
In APIs & Services > Library, search for and enable "YouTube Data API v3" for that project.
Open
3
Configure the OAuth consent screen
Under APIs & Services > OAuth consent screen, set up the app (external user type for most cases) and add the youtube.upload and youtube.force-ssl scopes.
Open
4
Create an OAuth client ID for a web application
Under APIs & Services > Credentials, create OAuth client ID credentials of type Web application, adding this app's redirect URI as an authorized redirect URI.
Open
5
Copy the Client ID and Client secret into this app
Paste the generated Client ID and Client secret into the YouTube provider's Client ID and Client secret fields, then click Connect to run the Google OAuth flow and authorize your channel.
6
Optionally set the default video privacy
Choose a default privacy (private/unlisted/public) in the Default video privacy field, understanding that unaudited apps are force-locked to private regardless.

App keys (set once in Settings)

Client ID
Google Cloud Console → APIs & Services → Credentials → OAuth 2.0 Client ID (Web application). Enable "YouTube Data API v3" and add the youtube.upload + youtube.force-ssl scopes on the consent screen first.
Client secretsecret
Same OAuth 2.0 client → "Client secret". Add app testers (or publish the consent screen) so accounts beyond you can connect.
Default video privacy
Unaudited apps are forced private regardless.

Good to know

The adapter only asks for YOUTUBE_CLIENT_ID and YOUTUBE_CLIENT_SECRET (config fields) plus an optional YOUTUBE_PRIVACY_STATUS default — there are no per-account credential fields; OAuth itself supplies the channel token.
There is NO community-post API — this integration can only upload a video. Community text, images, image polls, text polls, quizzes, and video-link posts must still be created in YouTube Studio.
Projects created after 28 July 2020 upload videos as force-private until the project passes Google's YouTube API Compliance Audit; setting privacyStatus to public/unlisted is silently overridden until then (source: developers.google.com/youtube/v3/guides/quota_and_compliance_audits).
While the consent screen is in Testing status, only test users you explicitly add can complete OAuth — publish the app (or add test users) before others try to connect.
Request access_type=offline and prompt=consent (already set by the adapter) so Google actually issues a refresh_token — without it, tokens expire and can't silently refresh.
Scopes requested are youtube.upload (video upload) and youtube.force-ssl (needed for posting comment threads); accounts connected before force-ssl was added will 403 on commentOn until reconnected.
The current Data API docs list videos.insert in a separate Video Uploads quota bucket; plan upload volume around that bucket and Google’s current quota page, not the old ~1600-unit general quota estimate.

Troubleshooting

Videos publish successfully but always show as Private on YouTube, even though "Public" or "Unlisted" was selected.: This is Google policy, not a bug: unaudited API projects have all uploads forced private. Submit your project for the YouTube API Services compliance audit in Google Cloud Console (Audit/Verification section of the API dashboard) to unlock the real privacy setting.
Posting a comment fails with a 403 (insufficient permission / insufficientPermissions on commentThreads.insert), even though video uploads work fine.: The connected account was authorized before the youtube.force-ssl scope was added, so it only has upload scope. Disconnect and reconnect the account to re-run OAuth consent and grant both youtube.upload and youtube.force-ssl.
Uploads start failing with a 403 quotaExceeded error, often after a batch of publishes in the same day.: Check the Google Cloud quota page for the YouTube Data API Video Uploads bucket. If the upload bucket is exhausted, wait for the reset or request more quota through Google’s YouTube API audit/quota process.
Upload fails with 403 uploadLimitExceeded even though the API project's quota looks fine.: This limit is per-channel, not per-API-project or per-key, and applies regardless of upload method. It resets on a rolling ~24-hour window — wait it out rather than trying a different client or key.

YouTube developer docs

YouTube — how to connect

Before you start

A Google Cloud project with the YouTube Data API v3 enabled, plus an OAuth 2.0 Client ID/Secret (Web application type) whose authorized redirect URI exactly matches this tool's callback — set as YOUTUBE_CLIENT_ID / YOUTUBE_CLIENT_SECRET.

A YouTube channel you can manage: during the Google consent screen you must sign in with the Google/brand account that owns or manages the target channel (the tool lists all channels that account can access).

The OAuth consent screen configured with the youtube.upload and youtube.force-ssl scopes, and — if the app is still in "Testing" publishing status — your Google account added as a test user, or the flow will be blocked.

A video file ready to attach: the YouTube integration is video-upload only. Community text, images, image polls, text polls, quizzes, and video-link posts are not publishable through the YouTube API.

Accept the forced-privacy caveat up front: until your Google Cloud project passes YouTube's API Services compliance audit, every uploaded video is force-locked to Private regardless of the privacy setting you choose here.

Step by step

Create or select a Google Cloud project

In the Google Cloud Console, create a new project (or pick an existing one) that will own the YouTube integration.

Open

Enable the YouTube Data API v3

In APIs & Services > Library, search for and enable "YouTube Data API v3" for that project.

Open

Configure the OAuth consent screen

Under APIs & Services > OAuth consent screen, set up the app (external user type for most cases) and add the youtube.upload and youtube.force-ssl scopes.

Open

Create an OAuth client ID for a web application

Under APIs & Services > Credentials, create OAuth client ID credentials of type Web application, adding this app's redirect URI as an authorized redirect URI.

Open

Copy the Client ID and Client secret into this app

Paste the generated Client ID and Client secret into the YouTube provider's Client ID and Client secret fields, then click Connect to run the Google OAuth flow and authorize your channel.

Optionally set the default video privacy

Choose a default privacy (private/unlisted/public) in the Default video privacy field, understanding that unaudited apps are force-locked to private regardless.

App keys (set once in Settings)

Client ID

Google Cloud Console → APIs & Services → Credentials → OAuth 2.0 Client ID (Web application). Enable "YouTube Data API v3" and add the youtube.upload + youtube.force-ssl scopes on the consent screen first.

Client secretsecret

Same OAuth 2.0 client → "Client secret". Add app testers (or publish the consent screen) so accounts beyond you can connect.

Default video privacy

Unaudited apps are forced private regardless.

Good to know

The adapter only asks for YOUTUBE_CLIENT_ID and YOUTUBE_CLIENT_SECRET (config fields) plus an optional YOUTUBE_PRIVACY_STATUS default — there are no per-account credential fields; OAuth itself supplies the channel token.

There is NO community-post API — this integration can only upload a video. Community text, images, image polls, text polls, quizzes, and video-link posts must still be created in YouTube Studio.

Projects created after 28 July 2020 upload videos as force-private until the project passes Google's YouTube API Compliance Audit; setting privacyStatus to public/unlisted is silently overridden until then (source: developers.google.com/youtube/v3/guides/quota_and_compliance_audits).

While the consent screen is in Testing status, only test users you explicitly add can complete OAuth — publish the app (or add test users) before others try to connect.

Request access_type=offline and prompt=consent (already set by the adapter) so Google actually issues a refresh_token — without it, tokens expire and can't silently refresh.

Scopes requested are youtube.upload (video upload) and youtube.force-ssl (needed for posting comment threads); accounts connected before force-ssl was added will 403 on commentOn until reconnected.

The current Data API docs list videos.insert in a separate Video Uploads quota bucket; plan upload volume around that bucket and Google’s current quota page, not the old ~1600-unit general quota estimate.

Troubleshooting

Videos publish successfully but always show as Private on YouTube, even though "Public" or "Unlisted" was selected.

This is Google policy, not a bug: unaudited API projects have all uploads forced private. Submit your project for the YouTube API Services compliance audit in Google Cloud Console (Audit/Verification section of the API dashboard) to unlock the real privacy setting.

Posting a comment fails with a 403 (insufficient permission / insufficientPermissions on commentThreads.insert), even though video uploads work fine.

The connected account was authorized before the youtube.force-ssl scope was added, so it only has upload scope. Disconnect and reconnect the account to re-run OAuth consent and grant both youtube.upload and youtube.force-ssl.

Uploads start failing with a 403 quotaExceeded error, often after a batch of publishes in the same day.

Check the Google Cloud quota page for the YouTube Data API Video Uploads bucket. If the upload bucket is exhausted, wait for the reset or request more quota through Google’s YouTube API audit/quota process.

Upload fails with 403 uploadLimitExceeded even though the API project's quota looks fine.

This limit is per-channel, not per-API-project or per-key, and applies regardless of upload method. It resets on a rolling ~24-hour window — wait it out rather than trying a different client or key.