Productivity
Google Sheets
A Google Sheets integration connects spreadsheets to Mobius so loops can read metadata, fetch values, append rows, update ranges, and clear ranges.
Use Google Sheets when the spreadsheet is a shared operational surface and the run needs structured rows or cells. Prefer table actions when Mobius should own the durable data model.
Capability map
| Capability | Value |
|---|---|
| Provider ID | google_sheets |
| Auth kind | oauth2_user |
| Connect flow | OAuth2 user grant or Google service account JSON |
| Actions | Yes |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | No |
Connect Google Sheets
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose Google Sheets, then use OAuth or a service account key. |
| CLI | The mobius CLI does not connect Google Sheets integrations yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/google_sheets/connect. Send an empty body for OAuth or service_account_json for service-account mode. |
Service-account mode is best for shared team spreadsheets. OAuth mode is best when the spreadsheet access should follow one user's Google permissions.
Actions
google_sheets.spreadsheet.get
google_sheets.values.append
google_sheets.values.batch_get
google_sheets.values.batch_update
google_sheets.values.clear
google_sheets.values.get
google_sheets.values.updateUse A1 ranges explicitly. Use append for log-like rows and update for stable
cells. google_sheets.values.clear removes cell contents, so keep it behind a
check or interaction when the range is dynamic.
Events
Google Sheets does not register source events yet. Start the run from a schedule, HTTP trigger, or another provider event, then call Sheets actions.
Next
- Compare with Mobius tables.
- Use action parameters from steps.
- Keep retries bounded with guardrails.