Integrations
Google integrations
Google integrations connect Google accounts, Google Ads accounts, or Google API keys to Mobius so loops can read, write, or react to Google products.
Use this page to choose the right Google provider before connecting a specific integration.
Provider map
| Provider | Connects with | Runs with | Use when |
|---|---|---|---|
| Gmail | Google OAuth or Workspace service account | Mailbox permissions | Incoming mail should start runs, or a run should draft, send, label, archive, or reply from a mailbox. |
| Google Calendar | Google OAuth | Calendar event permissions | Meeting changes should start runs, or a run should create, update, delete, or respond to calendar events. |
| Google Drive | Google OAuth | Drive file permissions | Selected Google Sheets or Docs files should emit update events. |
| Google Sheets | Google OAuth or service account | Spreadsheet permissions | A run should read or write spreadsheet values. |
| Google Ads | Google OAuth plus a Mobius server developer token | Ads account permissions | A run should query Ads data, generate Keyword Planner ideas, or change campaign status. |
| Google Places | Google Maps Platform API key or platform credential | Places API quota | A run should search places, nearby businesses, or place details. |
| Google Gemini | Google AI API key | Gemini API quota | Agents should use your Google AI account for Gemini models or media actions. |
When in doubt, connect the provider that owns the data the run needs to read or write. Use Google Drive only for file-change events. Use Google Sheets for cell data.
Credential model
Workspace providers use Google OAuth when the deployment has a shared Google OAuth app configured. Gmail and Google Sheets can also use a Google Workspace service account, which is better for team-owned mailboxes or spreadsheets where access should not depend on a human user's account.
Google Ads is separate from Workspace. It needs a Google OAuth user grant and a server-side Google Ads developer token. The project authorizes the Ads account in Mobius; the deployment supplies the developer token used on Ads API calls.
Google Places and Google Gemini use API keys. If a provider page says the project is using Mobius built-in credentials, usage counts against Mobius plan credits. If it says the project is using your key or account, upstream usage uses your Google quota and does not spend Mobius plan credits for that provider.
Disconnecting a Google OAuth integration removes the Mobius integration row. It does not revoke the Google grant, because multiple Mobius Google providers can share the same Google OAuth app and revoking the grant can break other connected Google integrations. Revoke the app from your Google account or Workspace admin console when you want to remove the upstream authorization.
OAuth setup
Google OAuth providers need these deployment variables before the Continue with Google button can complete:
GOOGLE_OAUTH_CLIENT_ID=...
GOOGLE_OAUTH_CLIENT_SECRET=...
GOOGLE_OAUTH_APP_BASE_URL=https://api.example.comGOOGLE_OAUTH_APP_BASE_URL must match the public API origin that receives the
provider callback. If Google returns redirect_uri_mismatch, compare the OAuth
client's authorized redirect URI with the callback URL shown on the provider
page.
Events and watches
Gmail, Google Calendar, and Google Drive emit source events. Google callbacks usually say that something changed, then Mobius fetches the changed object with the stored OAuth credentials before emitting the source event.
Google can send an initial sync callback when a watch is created. Mobius uses
that callback to confirm the watch and does not start loops from historical
state.
Next
- Connect Gmail for mailbox events and mail actions.
- Connect Google Ads for campaign and keyword research actions.
- Use source events to inspect incoming Google events.