The Google Workspace connector enables Omni to index and search content from your organization’s Google Workspace environment, including Drive, Docs, Sheets, Slides, and optionally Gmail.Documentation Index
Fetch the complete documentation index at: https://docs.getomni.co/llms.txt
Use this file to discover all available pages before exploring further.
Overview
What Gets Indexed
| Source | Content |
|---|---|
| Google Drive | Files, folders, and metadata |
| Google Docs | Full document text and comments |
| Google Sheets | Sheet names, cell content, and formulas |
| Google Slides | Slide text and speaker notes |
| Gmail (optional) | Email subjects, bodies, and attachments |
How It Works
- A service account with domain-wide delegation accesses Google Workspace APIs
- The connector syncs content based on user permissions
- Permission inheritance ensures users only see content they have access to in Google Workspace
The connector uses read-only access. Omni cannot modify any content in your Google Workspace.
Prerequisites
Before setting up the Google Workspace connector, ensure you have:- Google Cloud Platform account with billing enabled
- Google Workspace admin access (Super Admin or delegated admin)
- Google Cloud CLI (
gcloud) installed and authenticated (optional, for enabling APIs via CLI)
Setup
Step 1: Create a Google Cloud Project
- Go to the Google Cloud Console
- Click Select a project → New Project
- Enter project name:
omni-workspace-integration - Select your organization
- Click Create
Step 2: Enable Required APIs
In your new project, enable these APIs:Step 3: Create Service Account
- Go to IAM & Admin → Service Accounts
- Click Create Service Account
- Name:
omni-workspace-connector - Description:
Service account for Omni Google Workspace integration - Click Create and Continue
- Skip the optional steps and click Done
Step 4: Get the Client ID
- Click on the newly created service account
- Go to the Details tab
- Under Advanced settings, copy the Client ID (also shown as the service account’s Unique ID) — you’ll need this in Step 6 to authorize domain-wide delegation
Step 5: Create Service Account Key
- Go to the Keys tab
- Click Add Key → Create new key
- Select JSON format
- Click Create
- Save the downloaded key file securely
Step 6: Configure Domain-Wide Delegation in Admin Console
- Open the Google Workspace Admin Console
- Navigate to Security → Access and data control → API controls
- Click Manage Domain Wide Delegation
- Click Add new
- Enter the Client ID from Step 4
- Add the following OAuth scopes:
- Click Authorize
Step 7: Configure Omni
- Navigate to Settings → Integrations in Omni
- Find Google Workspace and click Connect
- Paste the contents of the service account key file from Step 5
- Enter your Google Workspace domain
- Enter the admin email address
- Click Connect, and click Configure against either the Drive or Gmail source
- Choose which sources you want enabled, select any specific users to include/exclude, and click Save Configuration
- Wait for the initial sync to complete
Your Google Workspace connector is now configured. Initial indexing may take a while, depending on the amount of content in your Google account.
Managing the Integration
Viewing Sync Status
Navigate to Settings → Integrations to view the sync status for each source directly on the list, including last sync time, number of indexed items, and any errors. Click Configure on a source for more details.Rotating Service Account Keys
It’s recommended to rotate service account keys every 90 days.- Create a new key in Google Cloud Console
- Update the key in Omni settings
- Delete the old key
Removing the Integration
- Navigate to Settings → Integrations
- Click Configure against the Google Workspace source
- Click Delete Permanently
- Optionally, delete the service account in Google Cloud and remove the domain-wide delegation entry in Admin Console
Troubleshooting
Insufficient permissions
Insufficient permissions
The setup requires:
- Project Creator - to create the GCP project
- Google Workspace Super Admin - for domain-wide delegation
API not enabled error
API not enabled error
APIs may take a few minutes to propagate after enabling. Check status:
Domain-wide delegation not working
Domain-wide delegation not working
Common causes:
- Client ID mismatch - verify the ID in Admin Console matches the service account
- Missing scopes - ensure all required scopes are added
- Propagation delay - wait 5-10 minutes for changes to take effect
- Wrong admin email - ensure the admin email has Google Workspace admin privileges
Sync taking too long
Sync taking too long
Initial sync duration depends on:
- Number of users in your organization
- Amount of content in Drive and Gmail
- API quota limits
Security Considerations
- Read-only access: The service account only has read permissions
- Permission inheritance: Users only see content they can access in Google Workspace
- Key security: Service account keys should be treated like passwords
- Audit logging: Enable Cloud Audit Logs to monitor API access
- Key rotation: Rotate service account keys every 90 days
What’s Next
Search Your Data
Learn how to search across Google Workspace content
AI Assistant
Ask questions about your documents and emails
Add More Connectors
Connect additional data sources