Connect Google#
Keep a working native login, or save the keys below.
godmode setup googleAccount access#
The bundled JSON entries are service-account private keys, not OAuth clients or user grants. For Ads, enable the API and obtain the required API access level in that Cloud project, then add the service-account email to the intended Ads account or manager. For Search Console, enable its API and grant the identity access to each property. Cloud IAM roles alone do not grant Ads or Search Console access.
Add credentials#
Save only the keys your product needs.
Drop the downloaded service-account JSON file into its prompt. Godmode reads and saves the JSON, leaving the source file in place. Your code must load the JSON with a supported library. See credential JSON.
Ads service account#
Give your agent an identity for Google Ads research and reporting.
Visit Google's service accounts
- Pick your Ads project, then open or create a service account.
- Select Keys > Add key > Create new key > JSON > Create.
Then add its email in Google Ads under Admin > Access and security.
Save as GOOGLE_ADS_SERVICE_ACCOUNT_JSON in Godmode.
Search Console account#
Give your agent an identity for reading your site's Search Console data.
Visit Google's service accounts
- Pick your Search Console project, then open or create a service account.
- Select Keys > Add key > Create new key > JSON > Create.
Then add its email to the property under Settings > Users and permissions.
Save as GOOGLE_SEARCH_CONSOLE_SERVICE_ACCOUNT_JSON in Godmode.
Check access#
- The consumer must parse the JSON variable and use an official Google auth/client library with the API's scopes; these variable names are Godmode conventions, not automatic Google SDK settings. Ads uses the adwords scope; Search Console uses webmasters or webmasters.readonly.
- List directly accessible Ads customers, then check the intended client/manager path. For Search Console, list sites and confirm the exact property and permission level. Only then run reporting, keyword planning or authorized management operations.
Restore access#
- Let the consuming Google library obtain and renew access tokens from the service-account key; ordinary access-token expiry needs no new key or browser consent. For a disabled, deleted or invalid private key, create a replacement on the same service account, save the matching Godmode entry, verify it, then retire the old key.
- User OAuth is a separate supported consumer choice: store its refresh grant under a separate name such as GOOGLE_SEARCH_CONSOLE_OAUTH_JSON. Reauthorize only when refresh fails because the grant is revoked, expired or policy requires sign-in. Save any replacement grant with godmode set NAME; Godmode does not write back refreshed credentials.
Provider docs#
- Ads service accounts and account access
- List accessible Ads accounts
- Search Console authorization
- List Search Console sites
- OAuth refresh and grant expiry
- Service account key rotation
Source: Godmode v0.20.0 provider catalog · 2026-11-13.