Claude with Google Docs, Sheets and Drive: the tip my relay video left out

In my video on the relay, I didn't even mention the Google Docs, Google Sheets and Google Drive integrations. They make your sessions a lot more persistent, and they let you share your work with people outside Claude. This is that follow-up.

If you haven't read how the relay works, start with how I run my work as a team of AI chats. The short version: each chat has one job, they all work from the same written notes, and one word passes work from one chat to the next.

Why I don't keep everything inside the chats

The relay I described in the video lives in a Claude project's files. The relay I use today is stronger, because it also runs through Google Drive. That gives me a second home for the work. If one of my projects were ever deleted, I would still have my relay.

There's a second reason. A lot of the people I work with don't use Claude. A Google Doc or a Sheet is something they can open, comment on and edit the way they always have.

What I keep in Google, and why

• Sheets for anything more than one project needs. My chats in different projects pass work to each other through a shared Google Sheet, one row per handoff. My writing rules live in a Sheet that every writing chat reads before it drafts. My content calendar is a Sheet too, so the plan and the posting record sit in one place.
• Docs for ideas. Every story idea lands as a Google Doc in one Drive folder: my own words first, then context, then open questions. The marketing chat reads the folder and picks up what's new.
• Drive as the backup. Anything I'd hate to lose, I make sure lives in Drive and not only in a chat.

None of that needs special software. It's the same Docs and Sheets I'd use anyway, with Claude reading and writing them.

What Claude can do with Google today

Here's what Anthropic's own pages said when I checked them on November 2, 2026.

Claude's Google Workspace connectors let it search and read your Drive, and there are separate Google Docs, Sheets and Slides connectors (also in beta) that can create new files and, on supported setups, edit them with you in a pane beside the chat. You turn them on from the plus menu in a chat, under Connectors, and sign in with Google. On Team and Enterprise plans, an owner has to switch them on for the organization first.

A few details matter for how I work:

• Claude reaches only what your Google account can. It doesn't get around your existing sharing.
• It asks first. By default, Claude asks before it shares a Drive file or sends an email.
• Drive files can live in a project. You can add Drive files to a private project's files, and per Anthropic's Drive page they're available in every chat in that project and refresh from Drive periodically when you open the project. That's what makes the work persist from one chat to the next. The option isn't offered in shared projects.
• Images inside a Doc are skipped. A Doc comes in as text. Sheets come in with every tab.

Anthropic also has a Claude add-on that runs inside Docs, Sheets and Slides, in beta, for working on the file you have open. It's a different thing from the connectors, and it can't share a file or give anyone access.

Sharing with people who don't use Claude

This is the part I use most. When a chat finishes something a client or a teammate needs, it goes into a Google Doc or Sheet, and I share that file the normal way. They never need a Claude account.

It also keeps the work in a format people trust. Some of my clients want to see the opportunities first, then the content in a Google Doc they can edit. That's where it goes.

Start with one Sheet

If you're running more than one chat, make one Google Sheet that holds where things stand: what's done, what's open, what's waiting and on whom. Connect Drive, and have every chat read that Sheet before it starts. When you need to share the work, it's already somewhere people can open.

If you want to see how I set up a whole team of chats for marketing, I walk through it on my Claude for marketing page.