Integrations / Content

Google Drive

Search files, read file details, export Google Docs as text or Markdown, create folders, and share files in Google Drive.

7 tools Connect with OAuth

Tools

google_drive.search_files

Search files and folders with a Drive query, e.g. name contains 'budget' and trashed = false. File IDs look like 1a2B3c4D5e6F7g8H9i0JkLmNoPqRsTuVw.

qorder_bypage_sizepage_tokencorpora

google_drive.get_file

Get a file's or folder's metadata by ID.

file_id*

google_drive.export_doc

Export a Google Doc's content as plain text or Markdown (up to 10 MB); for Google Docs only, not uploaded files.

file_id*mime_type

google_drive.create_folder writes

Create a folder, at the top of My Drive or inside a parent folder.

name*parentssupports_all_drivesfields

google_drive.share_file writes

Share a file or folder with a user, group, domain or anyone with the link.

file_id*role*type*email_addressdomainsend_notification_emailemail_messagesupports_all_drivesfields

google_drive.api_get

Send a GET request to any Google Drive API path under https://www.googleapis.com/drive/v3 and return the response. For endpoints the named tools don't cover.

path*params

google_drive.api_request writes

Send a POST, PUT, PATCH or DELETE request to any Google Drive API path under https://www.googleapis.com/drive/v3.

method*path*paramsbody

Tick Allow raw writes on the connection to add api_request, which can send POST, PUT, PATCH and DELETE requests to any Google Drive API path.

Connect

  1. In the Google Cloud console, create or pick a project and enable the Google Drive API under APIs & Services → Library.
  2. Under Google Auth Platform, fill in Branding, choose the Audience (Internal for a Google Workspace organization, or External with yourself as a test user), and under Data Access add the scope https://www.googleapis.com/auth/drive.
  3. This connection asks for the full drive scope rather than drive.readonly: searching and exporting every file only needs drive.readonly, but sharing a file or adding a folder inside an existing one needs write access, and drive.file would only reach files this connection created. Both drive and drive.readonly are restricted scopes, so a public app needs Google's verification and security assessment either way; Internal apps and test users don't.
  4. Under Google Auth Platform → Clients, create a Web application client and add the redirect URL shown on the connection page (https://<this app>/oauth/callback) as an authorized redirect URI.
  5. Paste the client ID and client secret on the connection, save, and use Connect to sign in with Google.
  6. While an External app's publishing status is Testing, only its test users can connect and Google expires their refresh tokens after 7 days.

Press Connect on the connection to approve access at Google Drive. Tokens renew automatically. How OAuth connections work

Credentials

OAuth client secret

Google Drive API docs

Your next automation is one sentence away.

14-day free trial with $5 of built-in AI included. Cancel anytime.

Start free trial Talk to us