SocialOAuth 2.0 (Google) + optional API keyPricing verified 2026-10-06
YouTube
Upload videos and Shorts, read and reply to comments, and read channel data.
AProvider definition
- Provider
- YouTube
- What it does
- Upload videos and Shorts, read and reply to comments, and read channel data.
- Why we need it
- Upload videos and Shorts, read and reply to comments, and read channel data.
- Used in
- Social (publish videos, comments) · Social listening (search)
BAccount requirements
- Account type
- Google account with a YouTube channel
- Prerequisites
- Google OAuth client (see Google Cloud Console)
- YouTube Data API v3 enabled
- Verification
- Uploads from unverified API projects created after July 2020 are locked to private until the project passes a YouTube API compliance audit.
CConnection method
- Authentication
- OAuth 2.0 (Google) + optional API key
- Credentials
- Uses the Google OAuth client (Google Cloud Console) credentials — no separate key.
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
- Per brand: App → Integrations → Connected accountsAnyone who manages the brand. Each brand connects its own accounts.
Setup steps
- 1Set up the Google OAuth client (see Google Cloud Console) with YouTube Data API v3 enabled.
- 2Add the YouTube scopes below to the OAuth consent screen.
- 3Integrations → Connected accounts → Connect YouTube and pick the channel.
- 4For public uploads, apply for the YouTube API Services audit.
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| openid | Identify the Google account. | Google sign-in for this product |
| Show which account is connected. | Google sign-in for this product | |
| https://www.googleapis.com/auth/youtube.upload | Upload videos and Shorts. | Google sign-in for this product |
| https://www.googleapis.com/auth/youtube.force-ssl | Read and reply to comments; update video metadata. | Google sign-in for this product |
| https://www.googleapis.com/auth/youtube.readonly | Read channel and video details. | Google sign-in for this product |
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Yes — free quota.
- Card or billing account required?
- No.
- Paid plan / costs
- No paid tier; request more quota through the YouTube API audit/extension form.
- Quota and usage limits
- Per project per day: 10,000 units for most calls, plus separate buckets of 100 videos.insert (uploads) and 100 search.list calls. comments.insert costs 50 units.
- Production restrictions
- Uploads stay private until the project passes the compliance audit.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/youtube/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
Nothing to enter for this product — it uses the Google OAuth client (Google Cloud Console) credentials. Connect it from the location in section C.
HTesting
- 1Connect the channel and upload a short test video as Unlisted/Private.
- 2Check Social → Comments shows comments from a recent video.
ITroubleshooting
| Problem | What to do |
|---|---|
| quotaExceeded | Daily quota used up — it resets at midnight Pacific time; request an increase via the audit form. |
| Video uploaded as private | The project hasn't passed the YouTube compliance audit. |
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved). |
| OAuth failure | Sign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app. |
| Redirect URI mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- myaccount.google.com → Security → Third-party apps → remove access; or disconnect in the application.
- Disconnect in the application
- App → Integrations → Providers & API keys or App → Integrations → Connected accounts → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- The connected channel's videos, comments and metadata.
Other Social providers
Facebook / Meta
OAuth 2.0 (Facebook Login) — App ID + App secret
Setup guide Instagram
OAuth 2.0 through the Meta app (Facebook Login)
Setup guide Threads
OAuth 2.0 — Threads app ID + secret
Setup guide LinkedIn
OAuth 2.0 — Client ID + Client secret
Setup guide X (Twitter)
OAuth 2.0 with PKCE — Client ID + Client secret (+ app bearer token for listening)
Setup guide TikTok
OAuth 2.0 — Client key + Client secret
Setup guide 
