At a glance
- Availability: Experimental (how to enable).
- Auth: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Scopes:
https://www.googleapis.com/auth/devstorage.read_only. - Optional scopes:
https://www.googleapis.com/auth/devstorage.read_write. - Docs: https://cloud.google.com/storage/docs/authentication
Credentials
Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.Setup
- Create or select a Google Cloud project: Go to https://console.cloud.google.com and create a project (new Google Cloud accounts include free-tier credit; Cloud Storage also has an always-free tier in some regions).
- Enable the Cloud Storage JSON API: Open https://console.cloud.google.com/apis/library/storage-json.googleapis.com and click Enable for your project.
- Create OAuth credentials: In https://console.cloud.google.com/apis/credentials create an OAuth 2.0 Client ID (Web application) and add your callback URL as an authorized redirect URI. Store the values as GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET.
- Create a test bucket: In https://console.cloud.google.com/storage/browser create a bucket and upload a small file so List Objects and Download Object have something to return.
- The default scope is read-only; uploading and deleting objects requires granting the optional devstorage.read_write scope during authorization.
- List Buckets needs the project ID (not the project name or number label shown in the console header dropdown).
- Object names that contain slashes must be URL-encoded (%2F) when used in the object path of download and delete calls.
Tools
Example prompts
- List the objects in one of my Cloud Storage buckets and summarize what’s stored there.
- Download a file from my Cloud Storage bucket and summarize its contents.
- List objects in a bucket with their metadata and point out large or old files I might want to clean up.