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 Docs through Google’s OAuth flow. Agents can read document content, create new documents, and edit existing ones. The gateway injects OAuth credentials into requests to the Google Docs API automatically. This is useful for agents that generate reports, draft documentation, or need to read information stored in Google Docs. To manage the files themselves (search, organize, share), see Google Drive.

​
What you will set up

  • A Google OAuth client shared by every Google app in OneCLI
  • A Google Docs connection authorized with your account
  • Per-agent, per-tool access, such as read-only for research agents

​
Connect Google Docs

This applies on OneCLI Cloud and self-hosted alike. 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.
Open Connections > Google Docs, select Connect Google Docs, pick your Google account, and click Allow.
OneCLI connect window for Google Docs showing Configuration required, the setup guide link, and the Configure credentials button.

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

​
What agents can do

  • Read the full text content of a document
  • Get document structure (headings, paragraphs, tables, lists)
  • Create new documents with formatted content
  • Insert, replace, or delete text in existing documents
  • Add and modify tables, headers, and footers
  • Apply text formatting (bold, italic, font size, color)
  • Insert images and links into documents
  • Read and add comments on a document

​
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 Docs.

​
FAQ

Yes. Follow the Google setup guide once. One client serves every Google app in OneCLI.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Yes. A read-only agent is a single grant. To manage the files themselves, use Google Drive.