domainwidedelegation.comStart free

Use cases → Documents and Drive

Aggregate all attachments from domain calendar events

Collect every file attached to calendar events across user calendars for compliance, knowledge search, or archival.

Who it is forCompliance teams, information managers, or automation engineers building cross-calendar search and backup.
APIsCalendar API, Drive API
Typical scopescalendar.readonly, drive.readonly

The problem

Attachments buried in calendar events are invisible to Drive and regular mail search, making them hard to audit or extract for legal or retention purposes. Manual checks miss files, and recurring events can multiply exposure.

How it works

  1. List all calendars for target users using the Calendar API.
  2. Enumerate events within the desired date range, capturing those with attachments.
  3. Extract attachment metadata, then fetch each file using the Drive API and its ID.
  4. Record the event context and deduplicate files referenced in recurring or copied events.
  5. Aggregate results into an index or export for downstream processing.

What changes

A single inventory of every file shared or attached via calendar events, mapped to their context and ready for audit or transfer.

The trap in this one. Attachments added by users as non-Drive files (like legacy Google Calendar links or external URLs) are only referenced as plain URLs in event data and cannot be fetched or audited by the service account. The Calendar API will return these as 'attachments', but only Drive-linked files provide file IDs resolvable by the Drive API—plan for missing content and unclear provenance.

Questions people ask

Does this include meeting recordings automatically?

No. Only attachments explicitly added to the event are surfaced. Meet recordings saved to Drive may be referenced by link, but are not attached unless a user does so manually.

How can I filter out duplicates from recurring events?

Track Drive file IDs and event IDs together. The same file can be attached to multiple instances; deduplicate by file ID, but keep context for each event.

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

Control access to meeting recordings with a service account

Enforce access policies on meeting recordings by adjusting Drive permissions automatically after each meeting concludes.

Extract attachments from Google Calendar events

Pull linked files from calendar events for compliance, migration, or downstream automation using a delegated service account.

Create a client folder structure the moment a deal closes

Provision a consistent Drive folder tree, seeded with templates and shared with the right people, automatically.