Google Drive

Find and analyze files instantly across Google Drive.

Family	Category	Sub-type	Auth type	Trending score
Productivity	productivity	file-storage	oauth2	84

Overview

Product URL	API docs	Supported features
https://workspace.google.com/products/drive/	https://developers.google.com/workspace/drive/api/guides/about-sdk	tool_discovery, health_check, approval_gated_writes

Setup

1. Install the connector instance.
2. Complete the OAuth authorization flow.
3. Sync the tools and test the connection.
4. Review approval-gated write tools before running them.

Auth & Configuration

This connector does not require additional instance config.

Available Tools

Tool	Requires approval	Description
list_files	No	List files and folders in Google Drive.
get_file	No	Retrieve metadata for a single file by its ID.
create_file	No	Create a new file in Google Drive with metadata.
share_file	Yes	Share a file by creating a permission entry.

Use list_files for the main execution example below because it is safe to run without approval.

Examples

Install

CLI

chainabit connectors install google-drive --name "Google Drive"

cURL

curl -X POST "$BASE_URL/connectors/instances" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "connectorKey": "google-drive",
  "displayName": "Google Drive"
}'

JavaScript

const response = await fetch(`${BASE_URL}/connectors/instances`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "connectorKey": "google-drive",
  "displayName": "Google Drive"
}),
});

Credentials

CLI

chainabit connectors auth <instance-id>

cURL

curl -X POST "$BASE_URL/connectors/instances/<instance-id>/oauth/initiate" \
  -H "Authorization: Bearer $TOKEN"

JavaScript

const response = await fetch(`${BASE_URL}/connectors/instances/<instance-id>/oauth/initiate`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
  },
});

Execute

CLI

chainabit connectors exec <instance-id> list_files --input '{}'

cURL

curl -X POST "$BASE_URL/connectors/instances/<instance-id>/tools/tool_list_files/execute" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {}
}'

JavaScript

const response = await fetch(
  `${BASE_URL}/connectors/instances/<instance-id>/tools/tool_list_files/execute`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${TOKEN}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
  "input": {}
}),
  },
);

Security Notes

• Keep tokens, API keys, and connection strings in the encrypted credentials vault.
• Do not allow arbitrary server URLs for remote MCP connectors.
• Mutating tools are approval-gated. Review the payload before executing them.

Troubleshooting

• If the health check fails, verify the token scope or credential payload and try again.
• If the tool list is empty, re-run sync-tools after storing the latest credentials.

Back to the catalog