Google Cloud

Google Cloud OAuth (shared)

1 min read·Updated July 28, 2026

Setup time

~2 min

Difficulty

easy

Who bills

Google

What it is

One Google Cloud OAuth client that Hi5Agents reuses across Calendar, Search Console, GA4, and Google Ads scopes.

Why Hi5Agents uses it

Google requires a verified OAuth app per project. Hi5Agents ships a shared verified client so ConciergeSched, InsightScope, and AdMiral all use the same consent flow — no per-agent verification pain.

Agents unlocked

One Google Cloud OAuth (shared) powers 4 agents. Typical cost Free.

ConciergeSchedRequired

Reads and writes Google Calendar events.

Scopes: https://www.googleapis.com/auth/calendar

RankBotRequired

Reads Search Console impressions, clicks, and queries.

Scopes: https://www.googleapis.com/auth/webmasters.readonly

PulseBoardUnlocks a mode

Reads Google Analytics 4 metrics. Internal-metrics mode works without it.

Scopes: https://www.googleapis.com/auth/analytics.readonly

AdMiralUnlocks a mode

Reads Google Ads (also needs your own Ads developer token). Meta-only guarding works without it.

Scopes: https://www.googleapis.com/auth/adwords (plus your own Google Ads developer token)

Building a stack? Try the stack builder or open the full matrix.

Setup steps

1Click 'Connect Google' from any agent that needs it.
2Approve the scopes for the specific agent (calendar, GSC, GA4, or Ads).
3The same connection is reused if another agent needs an overlapping scope.

Billing

Free from Google. Ads spend billed by Google directly if you run AdMiral in write mode.

Provider docs ↗

Was this accurate?Found an inaccuracy? We fix docs fast.

HubSpot private app

Meta (Facebook/Instagram) approvals