Skip to main content

Productivity

Productivity integrations connect AI Expedite to the calendars and file stores your team already uses. Two are supported today: Google Calendar (for the Meetings page) and Google Drive (for using files as agent context).

📷 Screenshot: Productivity-integration rows on Settings → Integrations.

Google Calendar​

Pull calendar events into Discover → Meetings so a recording can attach to the right event, and write back when an AI Expedite-recorded meeting completes.

Connecting​

  • From Discover → Meetings → Calendar tab — connect inline; the empty Calendar tab walks you through the OAuth handshake on first visit.
  • From Settings → Integrations — same handshake from the standard place.

The Google OAuth flow asks for read access to your primary calendar. Optional scope lets the platform write events back (for example, creating a "follow-up review" event on a participant's calendar after a meeting wraps).

What it powers​

  • The Calendar tab on Meetings — past and upcoming events rendered as a calendar; click an event to open the existing meeting record or start a new one bound to that event.
  • Pre-population — when you start a new meeting from a calendar event, attendees / time / title pre-fill from the event so you don't re-type.
  • Contact deduplication — participants from your calendar feed the Contacts tab on Meetings, deduplicated by email so the same person across multiple meetings shows up once.

Multi-calendar​

Connect multiple Google accounts when you have a personal calendar and a workspace calendar that both contain product-relevant meetings; the Calendar tab merges events from all connected accounts with the source visible on each event.

Google Drive​

Lets agents pull files from Drive as context — useful for spec docs, design files, or data that lives in Drive rather than as a workspace document.

Connecting​

  • From Settings → Integrations — the standard OAuth handshake.

The default scope is read-only on files you explicitly share with the connection (Google's "drive.file" scope), so the platform can only see files you've granted it access to — not your entire Drive. A broader scope is available if you want agents to access files without per-file sharing, but read-only-on-shared is the default for safety.

What it powers​

  • Drive-file references inside Agent Builder — add a Drive file as a reference in an agent step, and the file's content flows in as context at run time.
  • Document import — the Upload Document action on the Documents page accepts a Drive picker as an alternate source.
  • Per-file resolution — references resolve at run time, so if you update the Drive file, the next agent run reads the new version automatically. There's no caching layer to invalidate.

Removing the connection​

Removes the OAuth grant; agent runs that reference Drive files will fail at the reference step until you reconnect or remove the references. Files themselves are untouched on Google's side.