Work & OperationsDone with custom-built or unnamed agent Jan 1, 2026
Schedule meetings by email and update the calendar
The poster built an agent that reads emails, checks calendar availability, replies with a meeting time and adds it to the calendar.
- What They Did
- The poster built a background agent that scans their inbox for meeting requests, pulls the proposed date and time from the email, checks their calendar for conflicts, and either confirms the slot or suggests alternatives before blocking the time on the calendar. In comments, they said it uses limited permissions, no free-form actions, encrypted handling, and explicit authorization; for their use case it also accounts for in-person appointments, travel time, and distance between meetings.
- How It Went
- They said they had used it for about a month and estimated it saved 3–4 hours a week of scheduling. The main shortcoming raised in the thread was trust: people were uneasy about giving inbox access, and the poster did not share a detailed technical implementation.
- Worth Knowing
- The clearest practical catch is that this only made sense for them because existing scheduling tools did not handle travel time between in-person appointments.
Try it yourself with custom-built or unnamed agent
Build an agent that watches [email account] for meeting requests, checks my [calendar] for open slots in [working hours and time zone], and drafts a reply proposing a time. When the other person confirms, add the event to the calendar. Have it save replies as drafts for my approval before sending anything, and tell me when the setup is ready to test.
Do this with a skill.
These SkillShop playbooks do this exact job.