Skip to content
Writing
By Jeh··4 min read·Operator playbook

Claude in Workspace now edits your Docs and Sheets

Drafted through my n8n + AI pipeline, edited by me.

Claude in Workspace went into public beta on October 6, and it puts Anthropic's assistant inside Google Docs, Sheets, and Slides as a sidebar you work in, not a separate tab you copy results out of.

Two pieces shipped together. A sidebar add-on opens next to a file you already have open, and beta connectors let you start in Claude itself, paste a file link or ask for a new one, and have it build or edit a Doc, Sheet, or Slide from the chat window.

What actually changed

In Docs, Claude tightens sentences, restyles headings, and suggests rewrites through approval cards. In Sheets, it writes formulas, builds pivot tables and charts, adds tabs, and can run Python to join or clean data before writing the result back into the spreadsheet. In Slides, it builds new slides using a deck's existing layout and theme, and flags overlapping elements and text that runs off the slide.

Where Claude in Workspace pays off first for a service business

  • Proposal and SOW drafts built from a client's intake notes, inside the doc your team already shares
  • Pricing sheets and estimate templates with formulas fixed without a trip to a spreadsheet forum
  • Client-facing decks cleaned up for overlapping text and off-slide content before you hit send
  • Intake or onboarding sheets restructured without retyping a header row by hand

The setting to check before anyone touches a live file

Claude's access mirrors whatever Google sharing permissions already apply to a file, and the default mode is Ask before edits: every change waits for an approval card before it lands. An Accept all edits mode exists too, but it is worth leaving off until you trust the output on a given file type. On Team and Enterprise plans, an account owner has to turn the connectors on before anyone can use them, and admins can allowlist who gets the add-on at all.

Start narrow

Turn this on for one file type first. Pricing sheets or proposal drafts are a safe start. Leave Ask before edits on until you've watched it work through a few real edits.

A flow showing a request in Claude leading to a drafted edit, an approval card, a human approval, and the change landing in the live file.

  1. 01Trigger

    You ask in Claude or the sidebar

  2. 02Action

    Claude drafts the edit

    formula, slide, or rewrite

  3. 03Decision

    Approval card shown

    Ask before edits is the default

  4. 04Human

    You approve or reject

  5. 05Record

    Change lands in the live file

Ask before edits is the default: every change in Docs, Sheets, or Slides waits for your approval before it lands.

If your team already lives in Google Docs and Sheets for proposals, intake, and reporting, this is worth a look before year end. Tell me what that workflow looks like today and I'll help you find where an AI sidebar actually saves a step, and where it just adds one.

Building something this should run inside?

Book a call

Keep reading

Stay in the loop

The occasional system worth stealing, automation notes and the odd offer. No spam, unsubscribe anytime.