Google Drive

Connect Google Drive so your agents can read documents and folders from My Drive or Shared drives, and save outputs back into the same folders.

Audience: IT (the enabler) and builders

What it can do

  • Read. Files and folders.
  • Write. Two-way sync.

This integration does not support Triggers or Reply today.

Who connects this

Admin-enabled OAuth. IT sets up the Google Cloud project once. After that, builders OAuth their own drive.

Root access is not allowed by design. Builders must pick a specific folder. The bottom-of-dialog error is suppressed for this; a yellow Pick a folder badge is the signal to act on.

IT sets up the Google Cloud project and OAuth client

Create the Google Cloud project, configure the OAuth client, and approve the required scopes. Include the write scopes if Write is needed.

Builders OAuth their own drive

Once stage 1 is done, builders OAuth from within the platform.

Builder picks a specific folder

In the Project context, pick the specific folder. Decide whether the agent reads from My Drive or a shared drive.

What this article will cover

  • Setting up the Google Cloud project and OAuth client
  • Required scopes for Read and Write
  • Connecting and authorizing
  • Picking the specific folder to expose
  • Working with My Drive versus Shared drives
  • Verifying the connection
  • Common errors and how to resolve them