Chapter 4

3 Claude Connector Recipes for Drive, Gmail, and Calendar

2026-08-21 · 14 min read · 10 XP
Chapter 4 · Connecting AI: Stop Uploading, Start Linking

If You Connected It and Never Used It

"I connected it, but I don't actually know what to ask it to do."

Sound familiar? You hook up a connector, throw one question at it, and then never touch it again.

The real payoff of a connector isn't a single wow moment, it's what it saves you every single month. Today you'll run three recipes that put real work in front of Drive, Gmail, and Calendar. All three work on a free Claude web or desktop account. If you finished the last lesson, your connections are already in place and today's about putting them to work. If you haven't connected anything yet, start with the Claude connector setup lesson. This reflects how things stood in August 2026. What connectors can do keeps expanding, so if a screen doesn't match what's described here, check the official docs too.

Approval

The confirmation Claude asks for before it takes an action on your behalf. Per the official docs, the default is one approval per action. Sending, replying to, and forwarding an email, and sharing, moving, or trashing a Drive file, are the actions that typically require it.

Recipe 1: Drive, Turn Last Month's Report into This Month's Draft

In the web workspace track, you built a client report project and uploaded last month's report and brand guide to project knowledge by hand. That was the manual version. Now that a connector is in place, you can skip the upload step entirely. You don't need to have done that track first either, all you need is one document from last month sitting in your Drive.

Open a new chat and give it this:

Find last month's content performance report in my Drive. Match its section order and table structure to build a skeleton for this month's report. Leave the numbers blank, just note what data should go in each spot.

That's three jobs in one line: find, read, build. Claude searches Drive, finds the document, reads through it, and produces the skeleton. It shows you which document it drew from, and links back to the source when a link is available. If a link shows up, click through and check the skeleton against the original, that's part of the job too.

If the skeleton looks usable, turn it into a file.

Turn this skeleton into a Word doc and save it to my Drive.

Claude can build Excel (.xlsx), PowerPoint (.pptx), Word (.docx), and PDF files directly, and save them straight to Drive. That requires the code execution and file creation feature to be on. It's on by default for Free, Pro, and Max plans, so if it's off, flip it back on at Settings > Capabilities under Code execution and file creation. Team and Enterprise owners can turn it off at the org level, so if you hit a wall saving a file, check with your admin. Each file caps out at 30MB.

One limit worth knowing ahead of time: Claude only pulls text out of Drive files. It can't read a table or chart pasted in as an image, comments, or suggested edits left in Suggesting mode. If last month's report has its numbers as a screenshot instead of an actual table, those numbers won't get picked up. Keeping tables as tables is the safer bet.

Recipe 2: Gmail, Clear a Backlog and Draft Replies

Give the inbox everything at once and the answer turns into mush. Splitting it into two steps works better. Start with a sort.

Go through my unread emails and pull out the ones that need a reply this week. Put them in a table: who sent it, what they're asking for, and the deadline, one row per email.

Once you have the list, point at one.

Draft a reply to the second one. Suggest a time after next Tuesday, and save it as a draft in Gmail.

The draft lands in your actual Gmail account, and you can pull up your saved drafts later to check them. Up to this point, go ahead and click through any approval prompts without worrying, a draft hasn't gone anywhere yet.

Sending is where it gets different. As of August 2026, Claude can send, reply to, and forward Gmail messages. That's new, drafting used to be as far as it went. But the default is approval on every single action. Say "send this" and an approval prompt shows up first, nothing goes out until you click it. Get in the habit of checking the recipient, subject line, and first line of the body before you click through. Team and Enterprise owners can turn off the per-action prompt so it just runs, so if you're on a work account, it's worth asking your admin.

ChatGPT works the same way structurally. Its default permission level is Important actions, so reads happen automatically and it only asks before anything that leaves your inbox. OpenAI's own docs draw the same line: saving a private draft is a low-risk action, sending it to someone else is an important one. Different products, same line drawn in the same place.

One thing is flatly off-limits: attachment content. Claude can see an attachment's metadata, things like the file name and format, but not what's inside it. Ask it to summarize a quote that came in as an attachment and this is exactly where it stops. Moving that file to Drive first, or uploading it directly into the chat, is the workaround.

Recipe 3: Calendar, Booking Meetings and Getting a Briefing

Start with reading.

Give me a briefing on next week's calendar. Just pull out external meetings and deadlines, organized by day.

The calendar connector does more than look. It can create, edit, and delete events, find a time slot that works for everyone invited, set up recurring events, and respond to invitations you've received with an accept or decline. So you can ask for something like this:

Find an hour next week when Alex and I are both free, and book a meeting for Thursday afternoon. Title it "September Report Kickoff."

An approval prompt shows up here too. Calendar is where a mistake shows up in front of other people, a wrong meeting lands on someone else's calendar just as much as your own. Before you click through, check three things: the date, the time, and the attendees. Get those three right and anything else is an easy fix.

If event creation is flatly unavailable on your work account, that might not be you, it might be policy. On Team and Enterprise plans, an owner sets tool permissions per connector to Always allow, Needs approval, or Blocked. If your org has read open and write locked, there's nothing an individual account can do about it. Ask your admin.

Gemini can create events too. Google's help center lists creating an event in Google Calendar directly as an example of what a connected app can do. It also notes that with Personal Intelligence turned on, Gemini can go further and make recommendations or build a personalized schedule on your behalf.

CheckpointPick one of the three recipes and run it start to finish. Drive means finding last month's document and getting to this month's draft. Gmail means going from the reply list to a saved draft. Calendar means going from a briefing to a booked event. Notice where the approval prompts showed up along the way, remembering that is the real deliverable of this lesson.

Testing the Edges: What Works and What Doesn't

The fastest way to learn where the line is: ask for something that doesn't work and watch it fail. Try this:

Compare the three quotes attached to emails I got last month and put them in a table.

Claude finds the emails fine. What it can't do is pull the numbers out of the attachments. As covered above, a connector only reaches an attachment's metadata. Instead of rewriting the prompt ten different ways when the answer looks off, it's faster to stop here and take the workaround.

The official docs list five current limitations.

  • No access to Gmail attachment content, metadata only.
  • Some advanced Gmail filters aren't supported.
  • Complex requests get split into multiple API calls.
  • Google's API quotas still apply.
  • Performance gets inconsistent with a large mailbox.

Put together, the line falls in a predictable place. Finding, reading, and drafting are strong. Looking inside a file or scanning hundreds of items in one pass is weak. So break the job into smaller pieces. "Clean up my whole inbox" runs a lot worse than "just this week's unread mail."

Some limits are specific to one tool. ChatGPT can sometimes view a Drive file but not edit it. The official FAQ points to three reasons: the edit isn't supported in ChatGPT, the action is turned off, or ChatGPT doesn't have the Drive permission or OAuth scope it needs. A workspace admin turning off Drive actions falls into this bucket too. Gemini's variable is lag. Google's help center notes that deleting or editing an email in Gmail can take a few days to show up on Gemini's side. If you need Gemini to work off your just-cleaned inbox, give it a few days of buffer.

Making It Repeatable Every Month

To reuse a recipe that worked once, split it into two pieces. The room is the project, the data is the connector.

Reopen the client report project you built in the web workspace track. Project instructions hold the format and the rules: section order, notation conventions, sentence length, that kind of thing. For source material, attach the Drive original instead of a manually uploaded copy. Pick Drive when you add a file to the project and point it at the document, and that file stays synced with the Drive original from then on. Hunting down and re-uploading a new file every month disappears entirely.

Two caveats. Attaching a Drive document to project knowledge only works in private projects, that option is off in shared projects. And Personal Intelligence doesn't run inside Gemini Gems. Google's help center states plainly that Personal Intelligence isn't available in some features, Gems among them. Don't expect a connected app to produce a personalized answer inside a Gem, if you're building a recurring workflow there, uploading the material directly to the Gem is the reliable route.

One last recommendation. For a task that runs every month, stop at the draft and skip sending it automatically. Clicking through an approval prompt every time feels like friction, but cleaning up after one wrong email that actually reached a client takes a lot longer. Automate the reading, finding, and organizing. Keep the last click, the one that sends something out into the world, in your own hands.

This is exactly where the thing I wanted to do first fell apart. I'd connected Drive, asked Claude to create a document and drop it in a specific folder, and it only referenced Drive. It didn't create anything. At the time I chalked it up to connectors being read-heavy and left it at that.

It works now. The file-creation feature covered above showed up in the meantime, and Claude can save the Word, Excel, and PDF files it makes straight to Drive. This is an area where something that didn't work a few months ago works today, so if you shelved a task after hitting a wall once, it's worth trying again.

In 30 seconds
  • Three recipes: build this month's skeleton from a Drive report, sort a Gmail backlog into reply drafts, and go from a calendar briefing to a booked meeting
  • Claude can send, reply to, and forward Gmail, defaulting to approval on every action. Drafts save to your actual Gmail account, and you can pull up saved drafts later
  • Word, Excel, PowerPoint, and PDF files Claude creates save straight to Drive. Needs Code execution and file creation on at Settings > Capabilities, which is on by default even on the free plan
  • What doesn't work: Gmail attachment content, and images, comments, or suggested edits inside a Drive document. Break large jobs into smaller ones
  • To repeat it monthly: the room is the project, the data is the connector. A Drive document attached to a project stays synced with the original, private projects only

Frequently asked questions

Can Claude send emails?

Yes. As of August 2026, Claude can send, reply to, and forward Gmail messages. The default requires your approval before every one of these actions though, so nothing goes out until you click through the prompt. Team and Enterprise plans let an owner set it to run without asking every time.

Does Claude read Gmail attachments?

No. The official docs state it only reaches attachment metadata, things like the file name, not what's inside it. To work with an attachment's content, save it to Google Drive first and let the Drive connector read it, or upload it directly into the chat.

Can Claude book events on my Google Calendar?

Yes. Beyond viewing events, it can create, edit, and delete them, find a time that works for everyone invited, manage attendees, and set up recurring events. An approval prompt shows up before anything runs, so check the date, time, and attendees before you click through.

Can Claude save the files it creates straight to Google Drive?

Yes. Claude can create Excel (.xlsx), PowerPoint (.pptx), Word (.docx), and PDF files and save them to Drive. This works on every plan including free, and Free, Pro, and Max have it on by default. If it's off, turn on Code execution and file creation under Settings > Capabilities. Each file caps out at 30MB.

I'm on a work account and connector write actions aren't working

On Team and Enterprise plans, an owner sets tool permissions per connector to Always allow, Needs approval, or Blocked. If your org has write tools blocked, an individual account can't override that, so ask your admin. And even if Claude itself allows an action, it won't run if the underlying service doesn't grant that permission.

Sources (7)Expand to see all sources
quest_log.txt
Earned
Chapter 4 complete
+10 XP (total 0)
Connector writes aren't blocked, they just need your approval every time
0/5 · 0%
Lv.1 Novice
0 / 100 XP
100 XP to next level
Next questWhat Is MCP? The Standard Behind Your AI Connectors, Explained