Your inbox is where decisions pile up, and until now you've been copy-pasting between it and AI. In this episode, Jason connects Claude to Gmail using the official Google connector and shows the whole setup start to finish: browsing connectors, the OAuth sign-in, and the granular permission controls that let you decide what Claude can read, what needs your approval, and what's blocked entirely.
The core design principle: Claude drafts, you send. The connector can read, search, summarize, and prepare replies, but it cannot send email on your behalf. Jason demos a real inbox triage, sorting unread mail into needs-reply, can-wait, and ignore, then covers the trust calculus: compared to handing your inbox to a remote virtual assistant, Claude gives you tighter, per-tool controls and (covered in a future episode) a full log of every action it takes.
Connect Claude to Your Gmail
Connect Claude to Gmail and stop being the courier between your inbox and AI. Jason walks through setup, permissions, and a draft-first workflow where Claude prepares and you pull the trigger.
Transcript preview
We've talked about how connectors in Claude work, and really, they're doors. They're doorways to a completely different part of the world. Most of the time, this grants Claude access to the internet or to particular applications that you have access to, that you need your assistant to have access to. We give access to our calendars or our mailboxes to virtual assistants across the world all the time, and doing so with Claude is actually much safer, in my opinion. I'll show you some of the reasons why as we go through this video.The main thing I want to talk about is how we can leverage these t…
More on Claude
KEEP GOING
Claude Desktop Tour: Chat, Cowork, and Code
Tour the Cowork Tab: Tasks, Schedules, Skills, and Connectors
Don't Build, Describe: Adding Calendar Triage to Notion
Go Pro to watch →