Documentation Index
Fetch the complete documentation index at: https://docs.archal.ai/llms.txt
Use this file to discover all available pages before exploring further.
Twin ID: google-workspace
Covers Gmail, Google Calendar, Google Drive, Google Sheets, and Google Contacts. Error responses match the Google APIs format.
Gmail
| Tool | Description |
|---|
gmail_search_messages | Search messages by query (same syntax as Gmail search) |
gmail_get_message | Get a single message by ID |
gmail_get_thread | Get a conversation thread |
gmail_list_threads | List threads in a mailbox |
gmail_get_profile | Get the authenticated user’s email profile |
Calendar
| Tool | Description |
|---|
calendar_list_calendars | List all calendars |
calendar_list_events | List events in a calendar |
calendar_get_event | Get a single event |
calendar_get_free_busy | Check free/busy status for a time range |
REST API coverage
The twin also handles REST API calls to the Google API domains. Local harness runs start the TLS proxy by default (archal run --harness ...), so HTTP calls to these domains are redirected to the twin without any harness code changes. Pass --no-proxy to opt out when your harness wires twin base URLs directly through env vars.
gmail.googleapis.com — read, send, draft, label, trash, modify
calendar.googleapis.com — list, create, update, delete events
drive.googleapis.com — list, read, search files
sheets.googleapis.com — read and update spreadsheets
people.googleapis.com — contacts
oauth2.googleapis.com/token — OAuth refresh. The twin accepts any client_id / refresh_token pair and returns a synthetic access token bound to the seed’s primary account, so harnesses holding real-Google OAuth credentials boot without needing a twin-issued token.
The REST surface covers more operations than the MCP tools above. If your agent uses the Google client libraries directly, the proxy routes them to the twin so it can send emails, create drafts, manage labels, create calendar events, read Drive files, and update spreadsheets through the REST endpoints.
Interception depends on your harness runtime respecting HTTPS_PROXY and NODE_EXTRA_CA_CERTS (Node.js, Python requests, curl — all automatic). See Route-mode trust and safety for runtime compatibility and troubleshooting.
Seeds
| Seed | Description |
|---|
empty | Clean account |
assistant-baseline | Inbox with a few emails and calendar events |
gmail-busy-inbox | Many emails across categories |
calendar-packed-week | Busy calendar for scheduling tests |
calendar-conflict-resolution | Overlapping events for conflict-handling tests |
draft-send-cleanup | Drafts and sent items |
email-to-ticket-pipeline | Emails that map to external tickets |
multi-account-baseline | Multiple account setup |