When should you use it?
- You schedule many meetings by email
- Booking links feel too impersonal for your clients
- Your calendar is accurate
Not for: Meetings where the attendee list or agenda needs your judgment; Inboxes shared with others who also schedule
What do you need, and what do you get?
You need
- Inbox access to read meeting requests
- Calendar access to check and create events
- Your scheduling rules, such as working hours and buffers
You get
- Replies confirming or proposing free times
- Calendar holds for agreed meetings
- A notification for each scheduled meeting
How does it work, step by step?
- Spot requestsDetect emails that ask to meet and extract any proposed dates and times.
- Check your rulesApply working hours, buffers between meetings and days you don't take calls.
- Answer with real availabilityConfirm the proposed time if free, or offer two or three open alternatives.
- Block on agreementCreate the event only once the other side accepts, and tell you.
- Leave edge cases to youHand over anything involving several people, unclear time zones or important contacts.
The prompt
Our own prompt, inspired by u/BigFollowing9345 on r/SideProject and written to work in ChatGPT, Claude and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Read this email thread: {thread}. My calendar for the next two weeks: {calendar}. My rules: {rules} (working hours, buffer minutes, no-meeting days, time zone). If someone is asking to meet, extract proposed times with time zones. If one is free under my rules, draft a short confirmation. If not, draft a reply offering three free slots in their time zone. If there are several attendees, an unclear time zone, or the sender is in {vip_list}, don't draft; summarize it for me instead. Never create an event until the other person confirms.
Inspired by u/BigFollowing9345 on r/SideProject: I built an AI agent that reads my emails, schedules meetings, and updates my calendar automatically. Is this actually useful or just solving my own problem?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Time zones in emails are often implied; confirm them in the reply.
- Fast automated replies can surprise contacts who expected you to answer personally; consider a short delay or a draft-only mode at first.
Our take
The author's own questions are the right ones: would people trust this, and what would make them nervous. The trust problem is mostly about sending. Checking a calendar and proposing free times is low risk; replying instantly in your voice to a client is where mistakes show. So run it in draft mode for a couple of weeks, read what it would have sent, then allow automatic replies for routine requests from known contacts. Write your scheduling rules down explicitly, including buffers, focus time and how far ahead people can book, because the agent will only respect constraints it knows about. Time zones deserve a line in every reply, especially with international contacts. Meetings with several attendees or a sensitive context should always come to you. The payoff is real for anyone whose week is full of external calls, and the pattern is simple enough to build with an assistant that already has mail and calendar access.
Where the time goes back: He estimates three to four hours a week saved on scheduling back-and-forth.
FAQ
Isn't this what booking links do?
Does it send replies itself?
Source and credit
Inspired by u/BigFollowing9345 on r/SideProject. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I built an AI agent that reads my emails, schedules meetings, and updates my calendar automatically. Is this actually useful or just solving my own problem?
- Creator
- u/BigFollowing9345 on r/SideProject
- Published on
- Original date
- Dec 23, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.