What it does
Detects consecutive in-person meetings in Google Calendar, calculates travel time based on locations, and inserts buffer events so you’re never double-booked or racing across town.
Why I recommend it
Manual buffer blocks get forgotten, leading to late arrivals and frantic reschedules. Automation keeps your day sane and transparent to coworkers.
Expected benefits
- More accurate availability for assistants and schedulers
- Reduced late arrivals
- Fewer meeting overlaps or unrealistic itineraries
- Time set aside for rideshare/parking/logistics
How it works
When an event with a physical location is created -> script checks adjacent events -> Google Maps API calculates travel duration + padding -> create “Travel to [Meeting]” event before/after with correct color/status -> optional Slack DM reminding you to leave.
Quick start
Manually add travel events for a week to gauge typical duration, then codify the rules (add 15 min buffer minimum, etc.) before automating.
Level-up version
Account for real-time traffic via Google Maps, auto-book Uber/Lyft when travel exceeds walking distance, and notify meeting attendees if travel buffers cause conflicts.
Tools you can use
Calendar: Google Calendar
Maps: Google Maps API, Waze
Automation: Apps Script, Zapier, Calendly routing forms
Messaging: Slack, SMS for reminders
Also works with
Outlook calendars, executive assistant workflows, field service team scheduling.
Technical implementation solution
- No-code: Zapier monitors new events with location -> calls Google Directions API -> creates travel blocks via Google Calendar integration.
- API-based: Google Apps Script time-driven trigger scans calendars nightly -> inserts/updates travel events + sends summary email of next day’s itinerary.
Where it gets tricky
Handling multi-stop days, recurring events with different locations, collaborating calendars across time zones, and ensuring privacy when sharing travel buffers with others.
