SocialMati
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)

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

  1. 1console.cloud.google.com → create or select a project.
  2. 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.
  3. 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.
  4. 4Credentials → Create credentials → OAuth client ID → Web application; add every Authorized redirect URI shown below (social, calendar and ads).
  5. 5Copy the Client ID and Client secret; optionally create an API key restricted to YouTube Data API for listening.
  6. 6Enter them in the application, then connect each Google product from the brand's integrations.
  7. 7Before launch, submit the app for OAuth verification (Publishing status → In production).

DPermissions & API scopes

Scope / permissionWhy it's neededRequested by
openidSign the user in with OpenID Connect.Google sign-in for this product
emailShow which account is connected.Google sign-in for this product
https://www.googleapis.com/auth/youtube.uploadUpload videos and Shorts.Google sign-in for this product
https://www.googleapis.com/auth/youtube.force-sslRead and reply to comments; update video metadata.Google sign-in for this product
https://www.googleapis.com/auth/youtube.readonlyRead channel and video details.Google sign-in for this product
https://www.googleapis.com/auth/business.manageRead locations, publish posts and reply to reviews.Google sign-in for this product
https://www.googleapis.com/auth/webmasters.readonlyRead 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.readonlyRead reports and list properties. Read-only.Google sign-in for this product
openidSign the user in with OpenID Connect.Calendar booking
emailShow which account is connected.Calendar booking
https://www.googleapis.com/auth/calendar.eventsCreate, update and cancel the meetings the app books (with Meet links).Calendar booking
https://www.googleapis.com/auth/calendar.freebusyCheck availability without reading event details.Calendar booking
https://www.googleapis.com/auth/adwordsRead 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.

  1. Screenshot to add
    1. Account login / creation
    The provider's sign-in or sign-up page.
  2. Screenshot to add
    2. Developer console
    The developer console or dashboard home.
  3. Screenshot to add
    3. Project / app creation
    Creating the app or project used for this integration.
  4. Screenshot to add
    4. API enablement
    The API or product enabled for the project.
  5. Screenshot to add
    5. OAuth configuration
    Consent screen / OAuth settings with the redirect URIs.
  6. Screenshot to add
    6. API key / credentials creation
    Creating the key, secret or token (mask the value).
  7. Screenshot to add
    7. Permissions / scopes
    The scopes or permissions requested or approved.
  8. Screenshot to add
    8. Billing / quota settings
    Billing, credits or quota page.
  9. Screenshot to add
    9. Application connection
    The provider card in our application with fields filled (secrets masked).
  10. Screenshot to add
    10. Successful connection
    The 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.

FieldRequiredExample / defaultNotes
OAuth client IDYes—
OAuth client secretYes••••••••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

  1. 1Connect YouTube or Search Console from the brand's integrations; you should return to the app with the account listed.

ITroubleshooting

ProblemWhat to do
Error 400: redirect_uri_mismatchAdd the exact redirect URI (scheme, host, path) to the OAuth client's Authorized redirect URIs.
Access blocked: app has not completed verificationAdd the user as a test user, or complete OAuth verification.
API has not been used in project / is disabledEnable that API in APIs & Services → Library and retry after a few minutes.
Connection drops after 7 daysThe consent screen is in Testing — publish it to Production.
Invalid credentialsCheck the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure.
Missing permissionsReconnect 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 failureSign-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 mismatchCopy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings.
API not enabledEnable the API/product for the project or app in the provider console and wait a few minutes.
Quota exceededWait for the quota window to reset (see section E) or request a higher quota / add credits.
Account not eligibleCheck the account requirements in section B (e.g. business/professional account, verified property, registered organisation).
App review requiredPermissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions.
Billing requiredAdd 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.

Other Google providers

Start Free