Claude Google Sheets: Add-on, Connector, Claude Code, Zapier

Claude works in Google Sheets through Anthropic’s add-on, Claude for Google Workspace. It opens in a sidebar beside the sheet you have open, where it can explain how a total is built, fix a formula, clean up dates or build a model on a new tab. It is in beta on Pro, Max, Ultra, Team and Enterprise.

That is one of four ways to use Claude with Google Sheets. A Google Sheets connector lets Claude edit sheets from a Claude chat. Claude Code can read and write sheets through an MCP server. Zapier can send a new row to Claude and write the answer back. Every fact about Anthropic, Google tools and Zapier below comes from their own pages, read November 9, 2026.

The fifth option is ours. A Context Board Sheets board is a spreadsheet on the web that Claude and Codex fill in, for when a sheet is something several agents keep current. It has no live link to Google Sheets, and the last sections say exactly what that means. Context Board is ours, so weigh the bias.

Every way to use Claude with Google Sheets

Each route puts Claude in a different place. Pick the place first, and the setup follows.

Claude’s own routes all draw on your plan. Anthropic’s pricing page lists Pro at $20 a month, or $17 a month billed yearly, with Max from $100. A long session in a sheet counts toward the same limits as your chats, and our guide to Claude’s usage limits shows how fast they go.

Claude for Google Workspace: the add-on inside Sheets

This is the route most searches for “Claude for Google Sheets” mean. Anthropic released it in public beta on October 6, 2026, for Google Docs, Sheets and Slides at once. The Marketplace listing names Anthropic as the developer.

Set it up. From Anthropic’s help article:

1. Check that your Claude plan is Pro, Max, Ultra, Team or Enterprise, and that your Google account may install Marketplace apps.
2. Install Claude from the Google Workspace Marketplace. One install covers Docs, Sheets and Slides.
3. Open a sheet and choose Extensions, then Claude, then Open Claude.
4. Allow the two permissions Google asks for, then sign in with your Claude account.

Use Chrome, Edge or Safari. Firefox is not supported in the beta.

What it does in a sheet. It reads the open spreadsheet and any cells you select. Per Anthropic’s help article and launch post, it can:

• Explain how a total is built and flag hardcoded values.
• Write and fix formulas, and clean data, such as dates in mixed formats.
• Build a model on a new tab, with sensitivity tables and charts.
• Build pivot tables and native charts. For joins or cleaning, it pulls a range into Python and writes the result back.

How edits work. The default mode is Ask before edits: Claude describes each change and waits for Allow. Accept all edits lets ordinary changes go through without stopping, though links, outside images and access changes always ask. Edits land in the file’s version history under your name, like your own typing.

What it can’t do. It works only on the file you have open. It can’t open, create or copy other Drive files, or export a PDF. It can’t make triggers, custom menus or scheduled refreshes. The sidebar has to stay open, because closing it stops the task, and Google stops any one operation after six minutes. Chat history is kept in your browser for each file and does not follow you to another computer.

Where your data goes. Anthropic says the open file, your messages and attachments go to Claude, it does not train on that content, and inputs and outputs are deleted within 30 days except as its retention article describes. It is not for protected health information.

Older guides describe a different add-on, Claude for Sheets, with a =CLAUDE() cell function that ran on an Anthropic API key. Anthropic’s old docs address for it now forwards to a help page that returns “page doesn’t exist”, so this guide leaves it out.

Edit Google Sheets from a Claude chat with the connector

The add-on brings Claude into the sheet. The connector works the other way round: you stay in a Claude chat, and the sheet comes to you.

Anthropic’s Google Workspace connectors article treats Google Sheets as its own connector, separate from Google Drive. With it on, Claude can:

• Edit a Google Sheet live in a pane beside the chat, while you edit the same file.
• Create a new Google Sheets file.
• Re-read the sheet before each change. Anthropic still advises checking results in a busy file.

The pane works on Claude on the web in Chrome, and in Claude Desktop when its built-in browser is on. Anywhere else, the file card has Open in Google.

Turn it on.

1. In a Claude chat, click the plus sign.
2. Hover over Connectors and switch on Google Sheets.
3. Paste a sheet’s link, or ask for a new sheet and say “Google Sheet”. A plain request for a spreadsheet makes a local file instead.

If the connector is off when you ask, Claude asks you to connect it, then carries on. Claude reaches only the files your Google account can open, under your existing sharing.

The Drive connector reads; the Sheets connector edits. The Google Drive connector searches Drive and reads Sheets, along with Slides, PDFs and Office files, as text only. A sheet you add from Drive has to fit in Claude’s context window. Use it to bring numbers into a chat, and the Sheets connector to change them.

Plans. The article says the Google Workspace connectors are available to all users of Claude and Claude Desktop. On Team and Enterprise, an owner or primary owner has to turn them on for the organization first.

Claude Code and Google Sheets: an MCP server or the gws CLI

Claude Code is Anthropic’s coding agent in the terminal and IDE. To reach Google Sheets, you give it a tool. Our guide to MCP explains the protocol behind both options here.

Connectors you already added. Claude Code’s MCP docs say that if you log in to Claude Code with a claude.ai account, the connectors you added on claude.ai are available in Claude Code too, and /mcp lists them. That does not apply when an API key or a cloud provider such as Amazon Bedrock supplies the login.

An MCP server. mcp-google-sheets is an open-source, MIT-licensed server for Google Sheets and Drive. Its README lists tools such as get_sheet_data, get_sheet_formulas, update_cells, add_rows, create_sheet, create_spreadsheet and share_spreadsheet. Setup, per the README:

1. Create or pick a project in the Google Cloud Console.
2. Turn on the Google Sheets API and the Google Drive API.
3. Make a service account, download its JSON key, and share a Drive folder with the service account’s email as an Editor.
4. Add the server to Claude Code, using the syntax from Anthropic’s MCP docs:

claude mcp add --env SERVICE_ACCOUNT_PATH=/path/to/service-account-key.json \
  --env DRIVE_FOLDER_ID=your_folder_id \
  --transport stdio --scope user google-sheets \
  -- uvx mcp-google-sheets@latest

The README also offers OAuth for personal use, if you would rather sign in as yourself than share a folder with a service account. Start a new Claude Code session afterwards and ask, “Read the Costs tab of my Running costs sheet and add a row for the analytics tool at $19 a month.”

The gws CLI. gws is a command-line tool for all of Google Workspace, published under the googleworkspace name on GitHub and licensed Apache 2.0. Its README says it is not an officially supported Google product and expects breaking changes before v1.0. You install it with npm install -g @googleworkspace/cli, sign in with gws auth setup and gws auth login, and it ships agent skills you add with npx skills add. Claude Code then runs gws sheets commands in your terminal like any other tool.

A word of care for both. What the agent reads from a sheet goes to its model, and a sheet can hold text that tries to steer it. Use sheets you trust, and keep the service account’s folder narrow.

Zapier: send a new row to Claude and write the answer back

Zapier fits a narrow job well: every time a row lands in a sheet, ask Claude something about it and put the answer in the next column. A support inbox log, a list of new leads or survey replies all suit it.

The Google Sheets and Anthropic (Claude) page on Zapier lists the parts:

• Google Sheets triggers: New Spreadsheet Row, New or Updated Spreadsheet Row, Updated Spreadsheet Row, New Spreadsheet and New Worksheet.
• The Claude step: Send Message.
• Back to the sheet: Update Spreadsheet Row, Create Spreadsheet Row and Lookup Spreadsheet Row, among others.

So a Zap reads: New Spreadsheet Row, then Send Message to Claude with the row’s text, then Update Spreadsheet Row with the reply.

What it needs, per Zapier’s help center: a paid Anthropic account with API access, and an API key you make in the Anthropic Console and paste into Zapier.

A worked example: one founder’s running costs sheet

Take a solo founder with a Google Sheet called Running costs, with a Costs tab of every tool they pay for and a Revenue tab. The sheet and its numbers are an example. Over one week, the routes split like this.

1. Monday, in the sheet. The yearly total on Costs looks wrong. They open the add-on, select the total, and ask, “Why isn’t this 12 times the monthly total?” Claude explains how the total is built and flags a hardcoded figure in one row. They click Allow on the fix.
2. Tuesday, in a chat. Thinking about pricing, they ask Claude with the Sheets connector on, “Make a Google Sheet called Pricing test with three tiers and a monthly revenue column.” The new sheet opens beside the chat, and they change a price by hand while Claude adds the totals.
3. Friday, in Claude Code. With mcp-google-sheets set up, they ask Claude Code to add this week’s new invoices from a CSV in their project to the Costs tab. It calls add_rows and reports the new total.

Each route did its job. The gaps show up later. Every edit sits in version history under the founder’s name, so the history can’t tell Claude’s changes from theirs. Codex, which they use for the app, has none of this set up. And the costs sheet sits apart from the CRM and the dashboard they check each morning. Our guide to running a pipeline with Claude and our KPI dashboard examples cover those other two.

Claude Google Sheets not working? What to check

Most failures come down to the plan, the browser or an admin setting. Work down the list, from Anthropic’s two help articles.

1. Check the plan. The add-on needs Pro, Max, Ultra, Team or Enterprise.
2. Change browser. The add-on beta runs in Chrome, Edge and Safari. Firefox is not supported. The connector’s live pane wants Chrome on the web, or Claude Desktop with its built-in browser on.
3. “This application is not allowed by your administrator.” Your Google Workspace admin restricts Marketplace apps. They can add Claude to the allowlist, or install it for you from the Admin console.
4. “Access blocked: your institution’s admin needs to review Claude for Google Drive.” An admin goes to admin.google.com, then Security, Access and data control, API controls, Manage third-party app access. They add the OAuth app named Claude, set it to Trusted, and you reconnect after about 15 minutes. One approval covers Docs, Sheets and Slides.
5. On Team or Enterprise, nothing shows. An owner or primary owner turns the connectors on in Organization settings, Connectors.
6. A tab won’t read. Connected Sheets tabs of live BigQuery data can’t be read or edited. Use Data, Data connectors, Extract to pull the rows into a normal tab first.
7. An Excel file won’t work in the add-on. It works only on native Google files. Use File, Save as Google Sheets first.
8. A long job stopped. Google stops an operation after six minutes, and closing the sidebar stops it too. Split the job into smaller asks.
9. Still stuck. Go to Customize, Connectors in Claude, select the Google connector, click Disconnect, then sign in again on your next request.

A sheet your agents keep filling in: Context Board Sheets

Every route above is one Claude on one Google file. That fits most sheet work. It stops fitting when a sheet is something several agents keep up to date, like running costs that Codex updates from your app and Claude updates from your inbox, and you want to see who changed what.

Context Board is a web app at board.contextbolt.com, a workspace you share with your AI agents. A Sheet board is tabs of cells and formulas that your agents read and write over MCP. Claude, Claude Code, Codex and ChatGPT (on plans that allow a custom connector) work in the same sheet.

How it relates to Google Sheets. There is no live connection. From Google Sheets you choose File, then Download, and pick .xlsx, then import that file. It comes in as a copy, so later changes in Google Sheets don’t follow it, and edits on the board stay on the board. The board’s sheet supports the everyday Google Sheets functions, from SUM and IF to SUMIFS, XLOOKUP, FILTER and TEXTJOIN. QUERY, IMPORTRANGE and GOOGLEFINANCE are not supported.

What a Sheet board gives you:

• Every tab on import. Each tab arrives with its formulas, number formats, bold, borders, column widths, notes, links, dropdowns, checkboxes and merged cells. Fill colors and charts stay in the file, so ask your agent for a chart once the numbers are in.
• Agents that write. Your agent reads a tab as a table and writes cells, rows, formulas, formats and sorts, and adds totals as formulas.
• A name on every change. Cells an agent writes glow once in its color with its name. Board activity lists each change, and what an agent does can be undone.
• Charts that follow the sheet. Chart a range beside the cells, or put it on a Slides board, and the chart changes when the sheet does.
• Room to grow. A tab holds up to 10,000 rows and 104 columns, and a sheet up to 40 tabs.
• A file back out. Download a tab as CSV, or the whole sheet as .xlsx.

Set one up.

1. In Google Sheets, choose File, Download, Microsoft Excel (.xlsx).
2. In Context Board, choose New board, then Sheet, and use Import a CSV or Excel file on the left.
3. Connect your agent once. For Claude Code or Codex, link your computer with the one line from Connect. For Claude or ChatGPT, add the board’s address in the app and click Allow.
4. Ask for the work: “On my Running costs sheet, add the analytics tool at $19 a month to the Costs tab.” The row lands with its yearly total, glows in the agent’s color, and the totals move.

Context Board is free for 3 days, then $12 a month for every kind of board, sheets, docs, slides and dashboards included. Your agents work on the plans you already pay for, so there are no AI credits to buy.

What you give up. It is not Google Sheets. There is no live sync and no QUERY or IMPORTRANGE, and teammates who work in your Google Drive won’t see the board’s copy. If your sheet stays in Google and one Claude is enough, the add-on is the lighter choice. Weighing a database-style tool instead? Context Board vs Airtable compares the two.

Which way to pick

Pick by where the sheet lives and who has to touch it.

• Your sheet lives in Google and you work in it daily: the Claude for Google Workspace add-on. Select cells, ask, allow.
• You start in a Claude chat, or the job spans several files: the Google Sheets connector, with Drive on for reading.
• Your agent works in a terminal and the sheet is part of a build: Claude Code with mcp-google-sheets or gws.
• Every new row needs the same one question asked: a Zap with Send Message.
• Several agents keep one sheet current, beside the rest of your work: a Context Board Sheet, imported from your .xlsx download.

If your numbers are in Excel instead, our Claude in Excel guide covers Anthropic’s Excel add-in and an Excel MCP server. Otherwise, start with the add-on on a sheet you know well, ask it to explain one total, and check its answer against your own.