domainwidedelegation.comStart free

Use cases → Scheduling

Create team calendar events centrally with delegation

Automate event creation for groups by impersonating users or managing shared calendars with a service account.

Who it is forIT automation teams and internal tools engineers.
APIsCalendar API, Admin SDK
Typical scopescalendar, admin.directory.user.readonly

The problem

Manual event creation for every team is slow and error-prone, especially for recurring meetings, onboarding sessions, or shift rotas. Automating this centrally avoids missed invites and inconsistent event details.

How it works

  1. Configure domain-wide delegation on the service account with calendar and directory read scopes.
  2. Query group membership via the Admin SDK to identify users for each team.
  3. Impersonate each user and create events on their primary calendar, or use a shared calendar if appropriate.
  4. Send invitations or updates as required, handling batch creation for efficiency.

What changes

All team members receive events with correct details, and changes are handled consistently without giving every manager full calendar admin access.

The trap in this one. If the service account creates events directly on users' calendars without setting 'sendUpdates', attendees often do not receive invitations or updates—especially when impersonating. The Calendar API defaults to not sending emails, so events appear only in the calendar UI, which users may miss. Always specify 'sendUpdates' as 'all' when creating or updating events to ensure notifications go out, or you will get quiet user confusion with no error from the API.

Questions people ask

Should I use users' primary calendars or a shared team calendar?

Use a shared calendar for public or team-wide events. For personal or required-attendance events, create them directly on users' primary calendars.

Is there a rate limit when batch-creating events?

Yes, the Calendar API enforces per-user and per-project limits. Batch events in reasonable groups and monitor for HTTP 429 errors.

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 guide

Related use cases

Automate meeting room resource allocation with a service account

Assign and manage calendar-based room bookings across organisational units using a delegated service account, avoiding double-bookings and manual errors.

Provision calendar events based on group membership

Create or update events for all members of a Google Group by impersonating users with a service account.

Cancel events across many calendars at once

Bulk-cancel meetings for multiple users after a team change, departure or incident, using domain-wide delegation.