Google Drive

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: https://www.googleapis.com/auth/drive.readonly, https://www.googleapis.com/auth/drive.file.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
GOOGLE_CLIENT_IDYesGoogle OAuth Client ID Docs.
GOOGLE_CLIENT_SECRETYesGoogle OAuth Client Secret Docs.

Setup

  1. Choose who owns the Google OAuth app: On hosted Veryfront, Google Drive uses the Veryfront-managed Google OAuth app: connect Google Drive from the project's integrations and approve the Google consent screen, no environment variables needed. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET only to use your own Google OAuth app, which is required for local and self-hosted runs.
  2. Enable the Google Drive API: In the Google Cloud project that owns your OAuth app, enable the Google Drive API.
  3. Configure the OAuth consent screen: Configure the consent screen and add the scopes this connector requests. While the app's publishing status is Testing, only the test users you list can authorize it, and Google expires their refresh tokens after 7 days, so they must reconnect weekly. drive.readonly is a restricted scope, so publishing the app to external users requires Google's OAuth app verification.
  4. Create an OAuth client: Create an OAuth client ID of type Web application. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/drive for hosted Veryfront, or your app origin followed by /api/auth/drive/callback for a local or self-hosted app. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET from the app's credentials.
  5. Verify access: Run List Files (read-only). It returns files from the connected Google account without changing them.

Provider notes

Provider API reference.

Tools

ToolAccessDescription
List Files<br /><code className="reference-identifier">drive__list_files</code>ReadList files
Get File<br /><code className="reference-identifier">drive__get_file</code>ReadGet file
Search Files<br /><code className="reference-identifier">drive__search_files</code>ReadSearch files
Create Folder<br /><code className="reference-identifier">drive__create_folder</code>WriteCreate folder
Upload File<br /><code className="reference-identifier">drive__upload_file</code>WriteUpload file
Update File<br /><code className="reference-identifier">drive__update_file</code>WriteUpdate file
Delete File<br /><code className="reference-identifier">drive__delete_file</code>WritePermanently delete file
Download File<br /><code className="reference-identifier">drive__download_file</code>ReadDownload file (excludes Docs/Sheets/Slides)
Export File<br /><code className="reference-identifier">drive__export_file</code>ReadExport document text

Verify the connection

Call a read tool such as drive__list_files with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.