Delegate a calendar event without giving an agent write access to your calendar: narrow OAuth scopes, forward only the source email, and have the agent invite you from its own account.
Source episode · 14:31
How I AI: My 24 Hours with Clawdbot (aka Moltbot)—3 Workflows for a Powerful (and Terrifying) AI Agentwith Claire Vo
Claire rejects an overbroad Google OAuth request, forwards one event email to the agent’s account, and has the agent create the event on its own calendar and invite her.
A correct calendar invitation created by the agent, with source details, timezone, buffers, and no direct write access to your personal calendar.
Step by step
Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.
5 steps
Ask for calendar integration instructions, but state that the agent may read the required calendar and must not write to it. Enable only the Google API needed for that scope.
Help me connect your dedicated account to Google Calendar. You may read availability, but you may not create, edit, or delete events on my calendar. List the exact OAuth scopes you need before I authorize anything.
Inspect the OAuth consent screen. If it requests mail, files, contacts, deletion, or calendar writes that are not required, cancel and ask for a narrower authorization URL.
These requested permissions are broader than the scheduling task. Regenerate the authorization request with only the minimum read scope for the calendar and access to your own account.
AI agents will often request the broadest possible permissions. Always question if they are necessary for the specific task.
Forward the single confirmation email to the agent’s dedicated inbox. Ask it to extract the event title, date, start and end time, timezone, location, conference link, and suggested travel buffers.
Tell the agent to create the event on its own calendar and invite you. Require its assistant identity in any note and forbid changes to your personal calendar.
Create this event on your calendar and invite [my email]. Use the details from the forwarded source email, include the timezone and location, and add [buffer] before and after. Do not write to my calendar or send as me. Show me the resolved event details and event ID.
Treating the agent like a colleague by having it invite you is a safe and effective way to get events onto your calendar.
Compare the invitation with the source before accepting it. If anything is wrong, have the agent delete that event by ID and send one corrected invitation.
Turn an idea into a PRD, user stories, and a plan.
After the steps
How to recover when the loop fails and where human judgment helps.
Recover
Keep building
Instantly transform a fleeting product idea into multiple, high-fidelity interactive prototypes. This workflow uses collaborative AI bots to interpret a voice memo and screenshot, generating working code for rapid exploration.
Delegate tedious production design work to an AI assistant. This workflow shows how to use a custom bot connected to Figma to handle repetitive tasks like icon placement, freeing you up for more creative work, all from your phone.
Build a dynamic personal website that automatically updates with your latest check-ins. This workflow uses an AI bot to transform locations into unique 3D illustrations and publish them to your site, creating a living record of your life.
Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.