Add Google Meet recording access via Google Workspace API

[Peyton-Spencer]

Problem

Agents currently can't access Google Meet recordings from team meetings. This limits context gathering and makes it harder to catch up on discussions that happened in video calls.

Proposed Solution

Create a Google Workspace skill/integration that allows agents to:

1. List recent Google Meet recordings from the workspace
2. Download recordings for transcription/analysis
3. Access meeting metadata (participants, duration, timestamp)
4. Trigger on meeting end (optional: auto-fetch recordings when meetings conclude)

Prerequisites

• Google Workspace API access (not hard to set up)
• OAuth 2.0 credentials for workspace access
• Google Meet API or Google Drive API (recordings stored in Drive)

Implementation Ideas

Option 1: MCP Skill (Recommended)

Create a google-workspace skill similar to existing github or agent-browser skills:

• /workspace list-meetings - Show recent meetings with recordings
• /workspace get-recording <meeting-id> - Download specific recording
• /workspace transcribe <meeting-id> - Get recording + transcript

Option 2: Direct Integration

Add Google Workspace SDK to NanoClaw container:

• Use googleapis npm package
• Authenticate via service account or OAuth
• Expose as tool functions to all agents

Option 3: Dedicated Service

Run a separate microservice for Google Workspace access:

• Handles auth/refresh tokens
• Provides REST API for agents to query
• Can run on Sprites for always-on availability

Google Workspace API Setup

1. Create project in Google Cloud Console
2. Enable Google Drive API + Google Meet API
3. Create OAuth 2.0 credentials (or service account)
4. Grant domain-wide delegation (if using service account)
5. Store credentials securely (env vars or secrets management)

Use Cases

• Meeting summaries: Auto-generate summaries from recordings
• Action item extraction: Parse recordings for TODOs
• Context gathering: Agents can "watch" meetings they missed
• Searchable archive: Index meeting content for future reference

Recording Access Methods

• Google Drive API: Recordings are stored in Meet Recordings folder
• Calendar API: Link meetings to calendar events
• Admin SDK: Access workspace-wide meeting data (requires admin)

Related Work

• This complements Discord call recording (sibling issue)
• Could integrate with existing agent-browser skill pattern
• May need shared auth infrastructure for OAuth flows

Security Considerations

• Recordings may contain sensitive information
• Implement proper access controls (who can access what)
• Consider data retention policies
• Audit logging for recording access

[Peyton-Spencer]

Feature request for Google Meet recording access. Recommend starting with Option 1: MCP Skill approach to keep it modular. The Google Drive API path is simpler than trying to use Meet API directly since recordings are auto-saved to Drive.