From 43ee21134fb9f941691ec2f9a684acd3bdbd508e Mon Sep 17 00:00:00 2001 From: metatroncubeswdev Date: Wed, 21 Oct 2026 08:04:43 -0400 Subject: [PATCH] Use the approved GMB Audit project for Google Business Profile Co-Authored-By: Claude Opus 5.5 --- docs/google-app.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/docs/google-app.md b/docs/google-app.md index 4af7a52..626f861 100644 --- a/docs/google-app.md +++ b/docs/google-app.md @@ -1,4 +1,15 @@ -# Google app: Quorla (YouTube + Google Business Profile) +# Google apps: Quorla (YouTube + Google Business Profile) + +Two Google Cloud projects, both owned by dev@metatroncubesolutions.com: +- **YouTube** → project **Quorla** (`quorla`, number 275320055192), described below. +- **Google Business Profile** → project **GMB Audit** (`gmb-audit-489406`), which was **already approved** for the Business + Profile API (300 requests/minute). A new access request for `quorla` was declined because an approved project + already exists, so Quorla uses GMB Audit for Business Profile. Its consent screen was renamed to **Quorla** (logo, + links, domain quorlasocial.com), scopes openid / userinfo.email / business.manage, test users dev@ and the Gmail, and a + new web client **"Quorla GBP (app.quorlasocial.com)"** with redirect https://app.quorlasocial.com/oauth/gbp/callback. + Its keys are `GBP_CLIENT_ID` / `GBP_CLIENT_SECRET` in `.env`. + +## YouTube project (Quorla) - Google Cloud project **Quorla** (ID `quorla`, number 275320055192) in the **metatroncubesolutions.com** organization, created with dev@metatroncubesolutions.com. @@ -13,13 +24,12 @@ metatroncubesoftwaresolutions@gmail.com. Add each client's Google account here until the app is verified. - OAuth web client "Quorla web (app.quorlasocial.com)" with redirect URIs https://app.quorlasocial.com/oauth/youtube/callback and https://app.quorlasocial.com/oauth/gbp/callback. - Its ID and secret are in the PC's `.env` as YOUTUBE_CLIENT_ID/SECRET and GBP_CLIENT_ID/SECRET; copy those four lines + Its ID and secret are in the PC's `.env` as YOUTUBE_CLIENT_ID/SECRET (GBP_* now point to the GMB Audit client); copy those four lines to the server's `.env`, or enter them in Quorla → Connections → Set up. Google shows the secret only once; if it is lost, add a new secret on the client in Google Cloud. ## Still to do -1. **Business Profile API access**: request it (Google form) for project number 275320055192; until approved the - Business Profile APIs have a quota of 0. +1. ~~Business Profile API access~~ — done by reusing the approved GMB Audit project (see above). 2. **Verify quorlasocial.com in Google Search Console** (DNS TXT record) — required before Google verifies the app. 3. After deploy: **publish the app** (Audience → Publish app) and submit **verification** (sensitive YouTube scopes): Google asks for a demo video of the sign-in and how each scope is used.