Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to Google Sheets through Google’s OAuth flow. Agents can read spreadsheet data, write values, create new sheets, and manage formatting. The gateway injects OAuth credentials into requests to the Google Sheets API automatically. This is useful for agents that need to extract data from spreadsheets, generate reports, populate templates, or sync data between systems.

​
What you will set up

  • A Google Sheets connection through Google OAuth, in one click on OneCLI Cloud or with your own Google client
  • Automatic token injection on requests to the Google Sheets API
  • Per-agent, per-tool access, such as read-only for reporting agents

​
Connect on OneCLI Cloud (one click)

1

Go to Connections

Open the OneCLI dashboard and navigate to Connections > Google Sheets.
2

Authorize

Click Connect Google Sheets. You’ll go straight to Google: pick your account, review the permissions, and click Allow. No Google Cloud setup needed.
On self-hosted OneCLI, or to use your own Google client on Cloud, see Use your own Google client.

​
Use your own Google client

This is for self-hosted OneCLI, and for OneCLI Cloud when you choose Custom credentials instead of one-click. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.You paste the client into Connections > Google Sheets > Custom credentials, under the Redirect URI the guide asks you to register:
OneCLI Custom credentials card for Google Sheets with the setup guide link, the Redirect URI and its copy button, and the Client ID and Client Secret fields.

Custom credentials for Google Sheets in OneCLI.

Open Connections > Google Sheets, select Connect Google Sheets, pick your Google account, and click Allow.
OneCLI connect window for Google Sheets showing Configuration required and the Configure credentials button.

The Google Sheets connect window before a Google client is set up.

​
What agents can do

  • Read cell values from specific ranges (e.g., Sheet1!A1:D10)
  • Write values to individual cells or ranges
  • Append rows to the bottom of a sheet
  • Create new spreadsheets with specified titles and initial data
  • Add, rename, and delete sheets within a spreadsheet
  • Read and apply cell formatting (bold, colors, borders, number formats)
  • Create and manage named ranges
  • Read spreadsheet metadata (title, sheets, locale)
  • Clear cell contents in a specified range
  • Batch read or write multiple ranges in a single request

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Sheets.

​
FAQ

Yes. When you grant the connection, allow the read tools and block or require approval for writes. A read-only agent is a single grant.
No. The token stays in OneCLI, and the gateway adds it to Sheets API requests at the proxy. The agent makes plain HTTP calls and never holds the credential. See How it works.
Open Connections > Google Sheets in the dashboard and connect again with the account you want. Agents with access use the new connection automatically.
Not on OneCLI Cloud, where one-click connect works out of the box. Self-hosted, or to use your own client on Cloud, follow the Google setup guide once for all Google apps.