Use cases → Scheduling
Build a real picture of team availability
Read calendars across the domain to answer who is free, who is overloaded and where the week actually went.
| Who it is for | Managers scheduling across a team, and anyone doing capacity planning. |
|---|---|
| APIs | Calendar API |
| Typical scopes | calendar.readonly |
The problem
Free-busy views answer 'is this slot open' but never 'is this person drowning'. The data exists and nobody aggregates it.
How it works
- Impersonate each team member with a read-only calendar scope.
- Aggregate events by type, duration and attendee count.
- Publish a weekly view of committed time versus available time.
What changes
Scheduling decisions made against reality rather than against an empty-looking calendar.
Questions people ask
Can it schedule as well as read?
Yes, with the full calendar scope — but read-only is the right default for reporting.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Turn a finished meeting into follow-up automatically
Detect that a meeting happened, pull the notes, and draft the follow-up before anyone opens their laptop.
Turn a booking into a record everywhere it matters
When a meeting is booked, create the record, the folder and the confirmation in one pass.
Exporting calendar events and capacity domain-wide
How to reliably export all users' primary and secondary Google Calendar events for capacity analysis, with details on avoiding incomplete data and silent API omissions.