wehub-resource-sync
fed8b2eed7
Build and push multi-arch DocsGPT Docker image / build (linux/amd64, ubuntu-latest, amd64) (push) Has been cancelled
Backend release / release (push) Has been cancelled
Bandit Security Scan / bandit_scan (push) Has been cancelled
Build and push multi-arch DocsGPT Docker image / build (linux/arm64, ubuntu-24.04-arm, arm64) (push) Has been cancelled
Build and push multi-arch DocsGPT Docker image / manifest (push) Has been cancelled
Build and push DocsGPT FE Docker image for development / build (linux/amd64, ubuntu-latest, amd64) (push) Has been cancelled
Build and push DocsGPT FE Docker image for development / build (linux/arm64, ubuntu-24.04-arm, arm64) (push) Has been cancelled
Build and push DocsGPT FE Docker image for development / manifest (push) Has been cancelled
Python linting / ruff (push) Has been cancelled
Run python tests with pytest / Run tests and count coverage (3.12) (push) Has been cancelled
React Widget Build / build (push) Has been cancelled
74 lines
3.1 KiB
Plaintext
74 lines
3.1 KiB
Plaintext
---
|
|
title: Google Drive Connector
|
|
description: Connect your Google Drive as an external knowledge base to upload and process files directly from your Google Drive account.
|
|
---
|
|
|
|
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
|
|
|
|
<Steps>
|
|
|
|
### Step 1: Create a Google Cloud Project
|
|
|
|
1. Go to the [Google Cloud Console](https://console.cloud.google.com/) 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:
|
|
|
|
```env
|
|
GOOGLE_CLIENT_ID=your-google-client-id
|
|
GOOGLE_CLIENT_SECRET=your-google-client-secret
|
|
```
|
|
|
|
Add to your frontend `.env` file:
|
|
|
|
```env
|
|
VITE_GOOGLE_CLIENT_ID=your-google-client-id
|
|
```
|
|
|
|
| Variable | Description | Required |
|
|
|----------|-------------|----------|
|
|
| `GOOGLE_CLIENT_ID` | OAuth Client ID from GCP Credentials | Yes |
|
|
| `GOOGLE_CLIENT_SECRET` | OAuth Client Secret from GCP Credentials | Yes |
|
|
| `VITE_GOOGLE_CLIENT_ID` | Same Client ID, used by the frontend to show the Google Drive option | Yes |
|
|
|
|
<Callout type="warning" emoji="⚠️">
|
|
Make sure to use the same Google Client ID in both backend and frontend configurations.
|
|
</Callout>
|
|
|
|
### 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.
|
|
|
|
</Steps>
|
|
|
|
## 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.
|
|
|
|
<Callout type="tip" emoji="💡">
|
|
For production deployments, add your actual domain to the OAuth consent screen and authorized origins/redirect URIs.
|
|
</Callout>
|