# How to connect Google Docs to Grok Bot (no API keys) > Connect Google Docs to Grok Bot with ClawLink in one click — 33 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/google-docs Grok Bot runs on its own cloud computer, so most Google Docs guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Docs setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Docs actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect google-docs` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Google Docs. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Docs** — `npx -y @useclawlink/cli connect google-docs`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect google-docs # connect Google Docs (browser OAuth) npx -y @useclawlink/cli actions google-docs # list available actions npx -y @useclawlink/cli run google-docs --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect google-docs ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Google Docs to googledocs create document and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Google Docs is connected in the dashboard, that agent calls the same 33 Google Docs tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Google Docs MCP for Grok Bot Looking for a Google Docs MCP server for Grok Bot? ClawLink connects Google Docs to Grok Bot and exposes 33 Google Docs tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Google Docs integration](https://claw-link.dev/openclaw/google-docs) and the [Hermes Google Docs integration](https://claw-link.dev/hermes/google-docs) connect the same ClawLink account the same way. ## What the Grok Bot Google Docs integration can do 33 Google Docs tools are ready for Grok Bot once the account is connected. The 26 below are the ones people reach for most; your agent can call all 33. ### 26 of 33 Google Docs tools for Grok Bot | Tool | What it does | |---|---| | **Create document** `googledocs_create_document` | Create a new Google Docs document | | **Create document markdown** `googledocs_create_document_markdown` | Create a Google Docs document from Markdown | | **Export document as PDF** `googledocs_export_document_as_pdf` | Export a Google Docs document as PDF | | **Get document by ID** `googledocs_get_document_by_id` | Get Google Docs document metadata and structure | | **Get document plaintext** `googledocs_get_document_plaintext` | Get the plain text content of a Google Docs document | | **Insert inline image** `googledocs_insert_inline_image` | Insert an inline image into a Google Docs document | | **Insert page break** `googledocs_insert_page_break` | Insert a page break into a Google Docs document | | **Insert table action** `googledocs_insert_table_action` | Insert a table into a Google Docs document | | **Insert text action** `googledocs_insert_text_action` | Insert text at a specific position in a Google Docs document | | **Replace all text** `googledocs_replace_all_text` | Replace matching text everywhere in a Google Docs document | | **Search documents** `googledocs_search_documents` | Search Google Docs documents in Drive | | **Update document markdown** `googledocs_update_document_markdown` | Update a Google Docs document from Markdown | | **Update existing document** `googledocs_update_existing_document` | Update content in an existing Google Docs document | | **List spreadsheet charts** `googledocs_list_spreadsheet_charts` | Retrieve a list of all charts from a specified Google Sheets spreadsheet | | **Copy document** `googledocs_copy_document` | Create a copy of an existing Google Document | | **Create footer** `googledocs_create_footer` | Create a new footer in a Google Document | | **Create footnote** `googledocs_create_footnote` | Create a new footnote in a Google Document | | **Create header** `googledocs_create_header` | Create a new header in a Google Document, optionally with text content | | **Create named range** `googledocs_create_named_range` | Create a new named range in a Google Document | | **Create paragraph bullets** `googledocs_create_paragraph_bullets` | Add bullets to paragraphs within a specified range in a Google Document | | **Insert table column** `googledocs_insert_table_column` | Insert a new column into a table in a Google Document | | **Replace image** `googledocs_replace_image` | Replace a specific image in a document with a new image from a URI | | **Unmerge table cells** `googledocs_unmerge_table_cells` | Unmerge previously merged cells in a table | | **Update document section markdown** `googledocs_update_document_section_markdown` | Insert or replace a section of a Google Docs document with Markdown content | | **Update document style** `googledocs_update_document_style` | Update the overall document style, such as page size, margins, and default text direction | | **Update table row style** `googledocs_update_table_row_style` | Update the style of a table row in a Google Document | ## Example prompts **Googledocs Create Document** > Use Google Docs to googledocs create document and walk me through the result in plain English. **Googledocs Create Document Markdown** > Use Google Docs to googledocs create document markdown and walk me through the result in plain English. **Googledocs Export Document As Pdf** > Use Google Docs to googledocs export document as pdf and walk me through the result in plain English. **Googledocs Get Document By Id** > Use Google Docs to googledocs get document by id and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Docs working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Docs app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Docs through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Docs. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Google Docs actions to the runtime in a format your agent can reliably use. | 33 tools for Google Docs are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Docs to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Google Docs in the browser, and the 33 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Google Docs from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Google Docs tools Google Docs tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Docs call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Google Docs returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Google Docs and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Google Docs integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Docs: link your Google Docs account once in the browser and Grok Bot can call the Google Docs API through 33 ready-made tools — no custom code or token handling. ### How do I connect Google Docs to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect google-docs` to authorize Google Docs. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Google Docs to Grok Bot? About two minutes. Sign in, click Connect next to Google Docs in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Docs up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Docs working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Google Super](https://claw-link.dev/grokbot/google-super) — Unified access to multiple Google services in one integration - [Google Drive](https://claw-link.dev/grokbot/google-drive) — Upload, search, and manage files - [Google Analytics tools](https://claw-link.dev/grokbot/google-analytics) — Connect Google Analytics properties through hosted Google OAuth