import { Callout } from 'nextra/components' import { Steps } from 'nextra/components'

Google Drive Connector

Connect your Google Drive account to upload and process files directly as an external knowledge base. Supports Google Workspace files (Docs, Sheets, Slides), Office files, PDFs, text files, CSVs, images, and more. Authentication is handled via Google OAuth 2.0 with automatic token refresh.

Setup

Step 1: Create a Google Cloud Project

1. Go to the Google Cloud Console and create a new project (or select an existing one)
2. Navigate to APIs & Services > Library, search for "Google Drive API", and click Enable

Step 2: Create OAuth 2.0 Credentials

1. Go to APIs & Services > Credentials > Create Credentials > OAuth client ID
2. If prompted, configure the OAuth consent screen (choose External, fill in required fields)
3. Select Web application as the application type
4. Add your DocsGPT URL to Authorized JavaScript origins (e.g. http://localhost:3000)
5. Add your callback URL to Authorized redirect URIs:
   • Local: http://localhost:7091/api/connectors/callback?provider=google_drive
   • Production: https://yourdomain.com/api/connectors/callback?provider=google_drive
6. Click Create and copy the Client ID and Client Secret

Step 3: Configure Environment Variables

Add to your backend .env file:

GOOGLE_CLIENT_ID=your-google-client-id
GOOGLE_CLIENT_SECRET=your-google-client-secret

Add to your frontend .env file:

VITE_GOOGLE_CLIENT_ID=your-google-client-id

Step 4: Restart and Use

Restart your application, then go to the upload section in DocsGPT and select Google Drive as the source. You'll be redirected to Google to sign in, then can browse and select files to process.

Troubleshooting

• Option not appearing — Verify VITE_GOOGLE_CLIENT_ID is set in the frontend .env, then restart.
• Authentication failed — Check that the redirect URI matches exactly, including ?provider=google_drive. Ensure the Google Drive API is enabled.
• Permission denied — Verify the OAuth consent screen is configured and the user has access to the target files.
• Files not processing — Check backend logs and verify that backend environment variables are correctly set.