Google Drive
1. Google Cloud OAuth client
Section titled “1. Google Cloud OAuth client”Scopes:
https://www.googleapis.com/auth/drive.file— files created by the apphttps://www.googleapis.com/auth/drive.readonly— read any file the user shareshttps://www.googleapis.com/auth/drive— full access (only if needed)
Redirect: https://tappass.example.com/api/connect/google_drive/callback
2. Configure TapPass
Section titled “2. Configure TapPass”Reuses the same GOOGLE_OAUTH_CLIENT_ID / GOOGLE_OAUTH_CLIENT_SECRET as Gmail.
3. Connect
Section titled “3. Connect”Open GET /api/connect/google_drive (or use the dashboard) to start the OAuth flow. TapPass stores the credential in the vault.
Operations
Section titled “Operations”| Operation | Op group | Description |
|---|---|---|
list_files |
read | List files / folders |
get_file |
read | File metadata |
download_file |
read | Download file bytes |
search_files |
read | Search files by query |
create_file |
write | Upload a new file |
update_file |
write | Update an existing file |
list_permissions |
read | List sharing permissions |
Your agent never calls Google Drive directly. When the model requests a Drive operation as a tool call through the governed gateway, TapPass resolves the provider, fetches the connected credential from the vault, executes the operation, and audits the call. Write operations (create_file, update_file) are gated by your tool-decision policy.
PII handling for ingestion
Section titled “PII handling for ingestion”Content returned to the agent (e.g. download_file) passes through the same detection pipeline as everything else — detections are recorded in the audit trail and policy can redact or block.