Back to blog
AI Business Systems7 min read

Zapier MCP: Let Claude Edit Your Whole Google Drive

Claude can read your Google Drive but not edit it. Zapier MCP fixes that, so Claude rewrites Docs in place and turns a spreadsheet into a finished pitch deck.

Claude can read every single file in my Google Drive. It sees the folders, opens the docs, quotes them back to me. Then I ask it to change one line in a Google Doc and it can't.

So for months I did the slow thing. Claude wrote the paragraph, I copied it, I opened the doc, I pasted it in. Every time. The AI did the thinking and I did the clerical work.

Zapier MCP ended that. One connection gives Claude write access to Drive, and now it edits my documents where they live. It also does something I did not expect on the first try: it read a spreadsheet from a startup I co-founded and built a five page pitch deck out of it.

Why Reading Is Not Editing#

Claude Cowork ships with a Google Drive connector. Turn it on and Claude can find your files and read them. That part works.

Ask it to edit an existing Doc and you hit the wall. In my case Claude found the file, wrote a better outro, then told me it could not access the document natively. It offered workarounds instead: reach for the Drive API, try a Chrome plugin, or just hand me the text to paste myself. That last one is the copy-paste treadmill I was trying to get off.

The gap is simple. Native connectors mostly read. Acting on a file, editing it, creating a new one, filing it in the right folder, is a different permission, and Claude's own connector list does not cover it.

Zapier MCP covers it because Zapier already speaks to more than 9,000 apps. You get one connection into Claude and every app behind it, with per-action permissions so you decide exactly what the AI may touch. Worth saying plainly: the video this post comes from was sponsored by Zapier, and I have also paid for Zapier myself for over two years. It sits in my stack either way.

Setting Up Google Drive, Sheets, and Slides#

Start with a free Zapier account: Zapier MCP, 100 free tasks a month. That is enough to run everything below.

Open the MCP servers section and click add apps. Add Google Drive, then pick the permissions you want. You can hand over the narrow set, find a file, find a folder, get file permissions, if you are cautious about what an AI can reach. I switched everything on so I could show the full range.

Add Google Sheets and Google Slides at the same time. They matter later, and going back mid-task to grant a missing permission breaks the flow.

Try Zapier MCP Free
One connection puts Claude into 9,000+ apps with per-action permissions. The free plan includes 100 tasks a month, enough for everything in this guide.

Connecting it to Claude takes about a minute. In Zapier, create a new MCP server, choose your agent, and paste the prompt it gives you into Claude. Or go the other way: Claude settings, connectors, add new connector, search Zapier, connect, approve. Either path ends with Zapier showing as connected. The same setup works in Claude Code or ChatGPT Codex if that is where you work.

One feature that gets missed: click the three dots on Google Drive and you can change or add connections. Multiple Drive accounts, multiple Gmail accounts, all reachable from the same server. If you run a business account and a personal one, this is the reason to set it up this way.

Editing a Doc in Place#

I ran the exact prompt that failed before. Improve the outro of the script in this Google Doc.

This time Claude loaded the Zapier integration, confirmed it was connected to my Drive, and asked for one extra permission for Google Docs. I accepted, it added the connection itself, and then it read the doc and suggested what it would change before touching anything.

I approved. It rewrote the section, deleted the weaker version, and kept the better one. Version history shows the edit cleanly, the old scene removed and the new outro in its place. Small on its own. The point is that the file changed without me opening it.

The second pass was more useful. I asked Claude to research open source models and add a comparison section to the same script. It ran the research, found the right insertion point on its own, wrote a new scene with B-roll notes and voiceover, and pushed the old outro down a slot. I did not tell it where to put anything.

The Spreadsheet That Became a Pitch Deck#

This is the part that changed how I think about the setup.

Sitting in my Drive is a financial model from Contentup, a startup I co-founded years ago. Costs, revenue projections, a P&L, cash flow. Built well before the current AI wave, and untouched since.

I gave Claude two files, the financial projection and the old pitch, and asked it to turn them into a five page deck with an executive summary, key numbers, and projections, then save it to a specific folder in my Drive.

It used the Zapier integration to read both files and build the deck in Google Slides. The result has a headline and subheadline, an explanation of what the company does, the TAM, SAM, and SOM pulled out of the spreadsheet, and a chart it generated from the revenue projections with a written case for why the model works. Filed in the folder I named.

Three tools, Sheets to Slides to Drive, and I never opened any of them.

Closing the Loop With Notion and Gmail#

Drive is where it starts. The reason to run this through Zapier instead of a single connector is that everything else is already there.

I had Claude take that finished deck, draft a fundraising email to an investor address with the deck linked, and log the whole thing to my Notion CRM with a title, today's date, a draft status, and the recipient. It asked how to handle the email, I told it to create a Gmail draft, and a few actions later both existed.

The draft had the right recipient, a solid subject line, a concise pitch with real numbers from the model, and the link to the deck. The Notion database picked up the row and showed it on the board as in progress. If you trust it, you can skip the draft step and let it send. I keep the review step for anything going to a real person, which is the same reason scoping permissions tightly is one of the AI automation mistakes worth avoiding early.

If you want the inbox half of this, I built that first: giving Claude full access to your Gmail covers sorting, labeling, and drafting replies across multiple accounts.

What It Costs#

The free plan gives you 100 tasks a month, which covered the demos above with room left. If you run it daily, the Professional plan starts around $19.99 a month for 750 tasks. Scope your prompts to the files that matter and the free tier stretches further than you would guess.

Every prompt from the video is in my free Claude Cowork and Google Workspace Automation Playbook. If you want the deeper setup, honest limits, and 28 prompts, that lives in the Ultimate Claude Cowork and Zapier MCP Guide.

The unlock was never that AI can write. It already could. The unlock is that it can now put the writing where the work actually lives, and you stop being the copy-paste layer between the two.

Watch the full walkthrough on YouTube: https://youtu.be/hvg087GfO9o

ML
Moe Lueker
zapier mcpclaude google driveclaude coworkgoogle workspace automationspreadsheet to slides

Get new videos in your inbox

Weekly AI workflows. No fluff.

No spam. Unsubscribe anytime.

Want more guides like this?

Subscribe for new videos every week.

Subscribe on YouTube