GoogleOAuth 2.0 — Client ID + Client secret (optional API key for YouTube search)Pricing verified 2026-10-06
Google OAuth client (Google Cloud Console)
The single Google OAuth client used for YouTube, Google Business Profile, Search Console, Google Analytics, Google Calendar/Meet and Google Ads sign-in.
AProvider definition
- Provider
- Google OAuth client (Google Cloud Console)
- What it does
- Upload YouTube videos/Shorts and sync comments; publish Google Business Profile posts and reply to reviews; book CRM meetings on Google Calendar with Meet links.
- Why we need it
- The single Google OAuth client used for YouTube, Google Business Profile, Search Console, Google Analytics, Google Calendar/Meet and Google Ads sign-in.
- Used in
- YouTube · Google Business Profile · SEO (Search Console, GA4) · CRM calendar booking (Meet links) · Performance ads (Google Ads)
- Official site
- https://console.cloud.google.com/apis/credentials
BAccount requirements
- Account type
- Google Cloud project
- Prerequisites
- Google account
- Verified domain for the OAuth consent screen (for production)
- Verification
- OAuth app verification is required before external users can grant sensitive/restricted scopes (YouTube, Business Profile, Calendar).
CConnection method
- Authentication
- OAuth 2.0 — Client ID + Client secret (optional API key for YouTube search)
- 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).
Setup steps
- 1console.cloud.google.com → create or select a project.
- 2APIs & Services → Library: enable YouTube Data API v3, My Business Business Information API, My Business Account Management API, Google Search Console API, Google Analytics Data API, Google Analytics Admin API, Google Calendar API and (for ads) Google Ads API — only the ones you use.
- 3OAuth consent screen (Google Auth Platform): user type External, app name, support email, authorised domains, privacy policy and terms links; add the scopes listed below; add test users while in Testing.
- 4Credentials → Create credentials → OAuth client ID → Web application; add every Authorized redirect URI shown below (social, calendar and ads).
- 5Copy the Client ID and Client secret; optionally create an API key restricted to YouTube Data API for listening.
- 6Enter them in the application, then connect each Google product from the brand's integrations.
- 7Before launch, submit the app for OAuth verification (Publishing status → In production).
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| openid | Sign the user in with OpenID Connect. | 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 |
| https://www.googleapis.com/auth/business.manage | Read locations, publish posts and reply to reviews. | Google sign-in for this product |
| https://www.googleapis.com/auth/webmasters.readonly | Read search analytics, sitemaps and property list. Read-only — nothing is changed in Search Console. | Google sign-in for this product |
| https://www.googleapis.com/auth/analytics.readonly | Read reports and list properties. Read-only. | Google sign-in for this product |
| openid | Sign the user in with OpenID Connect. | Calendar booking |
| Show which account is connected. | Calendar booking | |
| https://www.googleapis.com/auth/calendar.events | Create, update and cancel the meetings the app books (with Meet links). | Calendar booking |
| https://www.googleapis.com/auth/calendar.freebusy | Check availability without reading event details. | Calendar booking |
| https://www.googleapis.com/auth/adwords | Read and manage campaigns, budgets and conversions. | Google Ads connection |
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Yes — no fee for the OAuth client; each API has its own free quota.
- Card or billing account required?
- No for these APIs (billing is only needed for paid Google Cloud APIs such as Speech).
- Paid plan / costs
- None for the APIs listed.
- Quota and usage limits
- Per-API quotas (see each Google product).
- Production restrictions
- In Testing status refresh tokens expire after 7 days and only test users (max 100) can connect.
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/google/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.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| OAuth client ID | Yes | — | |
| OAuth client secret | Yes | •••••••• | Stored encrypted; shown masked after saving. |
| API key (optional) | Optional | •••••••• | Enables YouTube search for social listening. |
Paste these into the provider's console
- Authorized redirect URI
https://api.socialmati.com/api/oauth/google/callback- Authorized redirect URI (Google Calendar for CRM)
https://api.socialmati.com/api/oauth/calendar/google/callback
HTesting
- 1Connect YouTube or Search Console from the brand's integrations; you should return to the app with the account listed.
ITroubleshooting
| Problem | What to do |
|---|---|
| Error 400: redirect_uri_mismatch | Add the exact redirect URI (scheme, host, path) to the OAuth client's Authorized redirect URIs. |
| Access blocked: app has not completed verification | Add the user as a test user, or complete OAuth verification. |
| API has not been used in project / is disabled | Enable that API in APIs & Services → Library and retry after a few minutes. |
| Connection drops after 7 days | The consent screen is in Testing — publish it to Production. |
| 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. Rotate the client secret in Credentials (add a new secret, update the app, then delete the old one).
- Disconnect in the application
- App → Integrations → Providers & API keys → 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
- Only the products a user connects, limited to the scopes listed on each product's page.

