Google OAuth review

Leafy Reviewer Test Page

Leafy uses Google OAuth as the account connection step. There is no separate Leafy username, password, registration form, or app-specific account database for reviewers to create.

Current review path

Google reviewers should test with their assigned Google review account, including Cindy dot mokko420123 at gmail dot com when that is the account supplied by the OAuth verification team.

If Google's consent screen reports that the account is not permitted, the account must be added as an OAuth test user or the app must be in a publish state that allows the reviewer account to continue.

App identity

OAuth app name

Leafy

Google Cloud project

kdo-calendars

Client ID

831892255935-uf3qnu3bbdldo0h0svm3lma6n9hncmmm.apps.googleusercontent.com

Homepage

https://leafy.kessler.io/

How to test

  1. Install gogcli. The full install guide is in the gogcli install docs. Common install commands: 
    brew install gogcli
gog --version

docker run --rm ghcr.io/openclaw/gogcli:latest version

git clone https://github.com/openclaw/gogcli.git
cd gogcli
make
./bin/gog --version
  2. Store the OAuth client JSON for the Leafy Google Cloud project: 
    gog auth credentials ~/Downloads/client_secret_....json
  3. Start the OAuth grant for the Google review account: 
    gog auth add <google-review-account> --services gmail,calendar,drive,docs,sheets,contacts,tasks
  4. Choose the Google account assigned to the reviewer.
  5. Review the requested Google API scopes on Google's consent screen.
  6. Approve consent to connect the Google account to the user's Leafy/OpenClaw connector runtime.
  7. Check the stored account and run representative read actions: 
    gog auth doctor --check
gog gmail search 'newer_than:7d' --max 10 --json
gog calendar events --today
gog drive ls --json
  8. After consent, Google redirects to the configured callback or landing page for this OAuth client.

gogcli connector usage

Leafy uses the open-source gogcli command-line connector inside the user's OpenClaw runtime. Source code and installation instructions are available in the openclaw/gogcli GitHub repository. The user starts an OAuth grant, approves Google's consent screen, and then the runtime stores the resulting token for that user's requested automations.

A typical operator flow is gog auth add to connect a Google account, followed by service-specific commands such as gog gmail, gog calendar, gog drive, gog docs, and gog sheets for user-requested actions.

Google reviewers do not need a separate Leafy password or registration account to evaluate this behavior. The important review step is the Google OAuth grant and the displayed scopes for this OAuth client.

Expected behavior

A successful test confirms that the reviewer can reach Google's OAuth consent screen for Leafy, see the exact requested scopes, and complete consent with a Google account. Leafy does not ask reviewers to create a second in-app account after Google sign-in.

The connected runtime uses the granted Google OAuth tokens to operate user-requested workflows for Gmail, Calendar, Drive, Docs, Sheets, Contacts, Tasks, and related Workspace APIs, limited to the scopes the user approves.

OAuth callback

If the review flow redirects to /oauth2/callback/, that route explains the callback result without exposing an authorization code or token in the page.

Open callback explainer Privacy Policy Terms of Service