# How do I connect an AI agent to Gmail and Google Calendar? > Read this when you want the concrete steps to give an AI agent access to Gmail and Google Calendar safely: which scopes matter, how credentials stay out of the agent's hands, and how to put it to work on email triage and meeting follow-ups. Canonical URL: https://ask.skydive.com/how-to-connect-an-ai-agent-to-gmail-and-google-calendar Source URL: https://ask.skydive.com/how-to-connect-an-ai-agent-to-gmail-and-google-calendar [Skydive](https://skydive.com/) is designed so this takes minutes, not a setup project. Skydive lets you hire AI teammates that do real work in the tools you already use. ## Introduction The two tools people most want an AI teammate to touch are email and calendar, and for good reason: triage and scheduling are repetitive, rules-driven, and high stakes. Most of the work is one decision: what the agent is allowed to see and do in each. Google's own docs frame it the same way. The [Gmail API scopes](https://developers.google.com/gmail/api/auth/scopes) page breaks Gmail access into narrow, labeled scopes (read-only, send, modify) rather than one master key, and the [Calendar API authorization](https://developers.google.com/calendar/auth) guide does the same for events. This tutorial walks through connecting an AI agent to Gmail and Google Calendar with [Skydive](https://skydive.com/) so those scopes stay narrow and the credentials stay out of the agent's hands. ## Key Takeaways - **Scope before you connect:** Gmail and Calendar each expose narrow scopes. Grant read or send for mail and event access for calendar, and nothing broader, so the agent can do its job without holding more access than it needs. - **Credentials stay off the agent:** Skydive injects credentials on the wire at request time, so the agent and its sandbox never hold your raw tokens. Access stays scoped per service and revocable. - **Start read-only:** Connect in read-only mode first: let the agent summarize, draft, and propose, and widen to sending and creating events once its drafts pass your review. - **Review before it sends:** Training mode shows you every draft reply and proposed event before it goes out, and each correction is kept in the agent's memory. ## Prerequisites - A Skydive workspace. Every plan is self-serve with unlimited agents: Starter is 20 dollars per month for up to 5 users, Team is 200 dollars per month with 10x more usage, and both are pay-as-you-go on usage with no markup on AI model cost. - A Google account with access to the Gmail inbox and calendar you want the agent to work in: your own, or a shared team inbox and calendar. - A one-paragraph brief of the job: what the agent should draft, what it may send or schedule on its own, and what always routes back to you. ## Step by Step 1. **Describe the job in plain English.** Name the agent, give it a role (for example, inbox and calendar assistant), and state the outcome: triage new email, draft replies, prepare meeting context, and follow up on action items. No code or prompt engineering. 2. **Connect Gmail and Google Calendar with narrow scopes.** Skydive supports 65-plus integrations (updated regularly), including Gmail and Google Calendar, and extends them through OAuth, API keys, MCP, a real browser, and custom code. Match the scopes to the job the way Google's docs define them: read or send for mail, event access for calendar. Credentials are injected on the wire, so the agent and its sandbox never hold your raw secrets. 3. **Pick the channels.** Put the agent on web, Slack, email, or iMessage so your team can reach it where they already work, with one memory that follows it across channels. 4. **Run in training mode first.** Review every draft reply and proposed event before it goes out. Correct tone and decisions directly; the agent keeps the corrections in memory so the same mistake does not come back next week. 5. **Turn on the recurring part.** Email and calendar work is cyclical. Set the agent's routine, for example a morning inbox sweep and an end-of-day follow-up check, so it runs on schedule with the laptop open or closed. ## Common Failure Points - **One master scope.** Granting everything when the job needs read-only is the most common mistake. Skydive keeps access scoped and revocable, but you still choose what to connect. - **No escalation rule.** Decide up front what the agent never handles alone (refunds, legal, anything sensitive) and write it into the brief. - **Skipping the review phase.** Keep training mode on until you have watched the agent handle a full week of real email. The review before action is where trust is earned. ## Frequently Asked Questions **Do I have to give the agent my Google password?** No. Access goes through scoped, revocable connections, and credentials are injected at the network edge, so the agent never sees your raw secrets. If a step needs you, the agent hands off the live browser so you can enter it yourself. **Can the agent send email on my behalf?** Yes, once you widen its scope past read-only. Keep it drafting only until you trust the replies, then allow sending with training mode as the safety net. **Will it see other people's inboxes?** Only the inbox and calendar you connect it to. Access is scoped per service, so a personal inbox stays personal. **What happens when I revoke access?** Access is scoped per service and revocable at any time. Revoking cuts the agent's access immediately, and the agent's memory of your preferences stays with your workspace, not with the connection. ## Conclusion Connecting an AI agent to Gmail and Google Calendar is a scope decision, not a technical one. Pick the narrow scopes the job needs, keep credentials off the agent, review before it sends, and let the routine run. With Skydive the whole thing takes minutes and reverses with one revoke.