Google Drive Connector — Integration Guide

Step-by-step instructions for syncing Google Drive folders to your agent corpus


What you'll set up	Sync a Google Drive folder as a knowledge source for your agent
Prerequisites	A Google Cloud project with OAuth 2.0 credentials configured
Time required	Approximately 10 minutes

Part A — Connecting Google Drive in the Corpus

Step 1 — Select Google Drive as a Knowledge Source

Navigate to your Corpus page and click Add +. In the modal that appears, locate the Sync Content section and select Google Drive.

Step 2 — Enter the Google Drive Folder URL

Navigate to the folder you want to sync, and copy its URL from the address bar. Paste the URL into the Google Drive Folder URL field. The URL must point to a folder — not an individual file.

ℹ Note: Example format: https://drive.google.com/drive/u/0/folders/<FOLDER_ID>

Step 3 — Enable Automatic Sync (Optional)

Toggle on Enable Automatic Sync if you want the corpus to stay up to date without manual intervention. When enabled, the system will re-index the connected folder every 30 minutes, automatically picking up any new, modified, or deleted files. You can leave this off if you prefer to trigger syncs manually.

Click the + Connect button. A Google sign-in popup will appear. Select the Google account that owns or has access to the folder you entered.

Step 5 — Grant Access and Continue

Google will display a consent screen listing the permissions the application is requesting (read access to your Google Drive files). Review the permissions and click Continue. If a warning states the app is unverified, click Continue again — this is expected for internally configured OAuth apps that are still in testing mode.

Step 6 — Verify Documents Are Synced

After authorizing, you will be returned to the Corpus page. The connected folder will now appear in the documents list with a Completed status, showing all files that have been indexed from that folder.

Step 7 — Sync or Delete the Connection

Inside the Google Drive sync panel you can manage connected folders at any time using the action buttons on the right of each row:

Action	Description
Sync (↻)	Immediately re-indexes the folder, reflecting any recent changes without waiting for the 30-minute automatic sync cycle.
Delete (🗑)	Removes the folder connection. You will be prompted to choose how to handle existing documents.

ℹ Note: When deleting a connection, choose one of the following options:
Keep all uploaded documents in the corpus — the files remain in the corpus but will no longer sync with Google Drive.
Delete all uploaded documents from the corpus along with the connection — all indexed files from this folder are permanently removed.

Part B — Google Cloud OAuth Configuration

Before users can authenticate, a Google Cloud project must be configured with an OAuth 2.0 client. Complete the steps below once per environment.

Step B1 — Create an OAuth 2.0 Client

Go to Google Cloud Console → Google Auth Platform → Clients and click + Create client. Select Web application as the application type.

Step B2 — Set Authorised Origins and Redirect URIs

In the client configuration, add the following values:

Field	Value
Authorised JavaScript origins	`{server-url}`
Authorised redirect URIs	`{server-url}/api/v2/mcp-sso/google/callback`

ℹ Note: To find server url, navigate to API Keys in the admin panel on Ejento

ℹ Note: After saving, copy the Client ID and Client Secret — you will need them in Step B5.

Step B3 — Add the Required OAuth Scope

Go to Data access in the left menu and add the following OAuth scope so the application can read Drive files:

Scope	Purpose
`https://www.googleapis.com/auth/drive.readonly`	Grants read-only access to all files and folder metadata in Google Drive

Step B4 — Add Test Users (if app is in Testing mode)

If the OAuth app is still in Testing publishing status (visible under Audience), only explicitly added test users can complete the sign-in flow. Navigate to Audience → Test users and click + Add users to add the email addresses of anyone who needs access. Note that the testing mode has a lifetime cap of 100 unique users — once reached, no new users can authenticate until the app is published.

Alternative — Internal app: If your organization uses Google Workspace and the Google Cloud project was created under your Workspace domain, you can switch the app to Internal user type (via the Make internal button on the Audience page). Internal apps are automatically trusted by all users in that domain, bypassing the test user list and the 100-user cap entirely. This is the simpler option for organizations where everyone signing in belongs to the same Workspace domain.

ℹ Note: Once all users are onboarded and the app is ready for production, click Publish app on the Audience page to remove the testing restrictions and user cap.

Step B5 — Integrate Google App with Ejento

After completing the OAuth client setup, kindly provide your Client ID and Client Secret to your account representative. These credentials are required to complete the integration configuration.

For questions about scope requirements or OAuth app verification, refer to the Google Identity documentation.

Google Drive Connector

Google Drive Connector — Integration Guide#

Part A — Connecting Google Drive in the Corpus#

Step 1 — Select Google Drive as a Knowledge Source#

#

Step 2 — Enter the Google Drive Folder URL#

Step 3 — Enable Automatic Sync (Optional)#

Step 4 — Click + Connect and Sign In#

Step 5 — Grant Access and Continue#

Step 6 — Verify Documents Are Synced#

Step 7 — Sync or Delete the Connection#

Part B — Google Cloud OAuth Configuration#

Step B1 — Create an OAuth 2.0 Client#

Step B2 — Set Authorised Origins and Redirect URIs#

Step B3 — Add the Required OAuth Scope#

Step B4 — Add Test Users (if app is in Testing mode)#

Step B5 — Integrate Google App with Ejento#