xAI has released documentation detailing the functionality of Grok's connectors for Google Drive, Gmail, and Google Calendar. These connectors allow Grok to interact with users' Google accounts, enabling various operations directly within conversations.
The Google Drive connector, for instance, permits Grok to search, read, create, and manage files. Similarly, the Gmail and Google Calendar connectors facilitate email and schedule management.
Key Points
- The Google Drive connector allows Grok to search, read, create, and manage files in Google Drive.
- Grok can find Google Drive documents by content or title, read their contents, create new files, organize folders, and upload artifacts.
- The Gmail connector enables searching emails, reading full messages, composing and managing drafts, sending messages, and organizing mail.
- Gmail and Google Calendar connectors use tiered permission models, with write capabilities progressively enabled.
- The Google Calendar connector allows searching events, viewing details, checking availability, creating, updating, and deleting events, and RSVPing.
- xAI states it does not train its models on user data from Google Drive, Gmail, or Google Calendar.
- User files and documents are not stored on xAI servers; Grok accesses data in real time and does not retain it afterward.
Context
According to xAI documentation, these connectors utilize Google OAuth and request specific scopes during sign-in. Users see a consent screen listing the permissions, and Grok can only access files or data that the signed-in Google account has access to. For Grok Business and Enterprise plans, a team admin must provision connectors in the cloud console before team members can use them, as stated by xAI.
Why It Matters
These connectors expand Grok's utility by integrating directly with widely used Google services, allowing users to manage their digital workspace through conversational AI. Builders can note the explicit statements regarding data privacy and control, which address common concerns about connecting AI models to personal data.
What To Do
- Review the specific permissions requested by each Grok connector during the Google OAuth sign-in process.
- Note that Gmail and Google Calendar have tiered permission models, with write capabilities requiring additional enablement.
- For Grok Business and Enterprise users, confirm with team admins that necessary connectors are provisioned in the cloud console.
- Understand that users can revoke Grok's access to their Google accounts at any time through Grok's settings or directly via Google's permissions page.