Integration · Cloud and hosting
AI agents for Google Cloud (sign in with Google)
Every Google Cloud API from one connection, signed in with your own Google account instead of a service account key.
- Actions
- 7
- Read
- 4
- Write
- 3
Actions
What your agents can do in Google Cloud (sign in with Google)
Every Google Cloud API from one connection, signed in with your own Google account instead of a service account key: Compute Engine, Cloud Storage, BigQuery, Cloud Run, GKE, Cloud SQL, Pub/Sub, IAM, Vertex AI and two hundred more. Find a service and an operation, read its parameters, and run it, from Google's own API Discovery documents. Calls can do what your IAM roles allow, within the connection's Access.
Read 4
Look things up. Nothing changes.
List services
Lists the Google Cloud services this connection can call, each with its id (the service every other action takes, like compute, storage or bigquery), name, category and number of operations.
Search operations
Finds Google Cloud operations by what they do, across every service or inside one: "list virtual machines", "read a secret", "delete a bucket".
Describe an operation
Reads one Google Cloud operation's contract from the vendor's own API model.
Run a read operation
Runs one Google Cloud read operation (Describe, List, Get and the like: nothing changes) and returns its answer as JSON in result.
Write 3
Create, change or send.
Run a write operation
Runs one Google Cloud operation that creates or changes something (Create, Put, Update, Start, Tag, Send and the like) and returns its answer as JSON in result.
Run a destructive operationDeletes data
Runs one destructive Google Cloud operation: deletes, terminations, stops and restarts, key regeneration and permission changes, which cannot be undone by another call.
Run an operation on secretsDeletes data
Runs one Google Cloud operation that returns or sets secrets.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Sign in with Google and approve access (OAuth).
Settings
- Default project
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Google Cloud (sign in with Google) data
Ask a question in plain words. The agent can list services, search operations or describe an operation in Google Cloud (sign in with Google), then answers with what it found.
- 02
Let an agent update Google Cloud (sign in with Google)
Have the agent run a write operation or run a destructive operation in Google Cloud (sign in with Google) as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Google Cloud (sign in with Google) and Slack: it can list services in Google Cloud (sign in with Google) and post a summary to a Slack channel in the same run.
Works well with
More Cloud and hosting tools
- Amazon Web Services7 actionsEvery AWS service from one connection: EC2, S3, Lambda, RDS, DynamoDB, IAM, ECS, EKS, CloudWatch, Bedrock and over four hundred more.
- Microsoft Azure7 actionsEvery Azure service from one connection: Virtual Machines, Storage, App Service, Functions, AKS, SQL, Cosmos DB, Key Vault, Networking, Monitor, OpenAI and every other resource provider of Azure Resource Manager.
- Google Cloud7 actionsEvery Google Cloud API from one connection: Compute Engine, Cloud Storage, BigQuery, Cloud Run, GKE, Cloud SQL, Pub/Sub, IAM, Vertex AI and two hundred more.
- Amazon S38 actionsList buckets and files, read and download files, upload any file, save JSON files and delete files in Amazon S3 (Simple Storage Service), signed with an AWS access key.
- Netlify5 actionsList sites and their deploys, start a build, check a deploy's status, and roll a site back to an earlier deploy, on the Netlify teams a personal access token can reach.
- Heroku16 actionsSee Heroku apps, dynos, releases and builds, restart dynos, scale process types, roll back a release and switch maintenance mode, with a Heroku API token.
FAQ
Google Cloud (sign in with Google) and MyDeepAgents
Can MyDeepAgents connect to Google Cloud (sign in with Google)?
Yes. The Google Cloud (sign in with Google) connector has 7 actions: 4 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Google Cloud (sign in with Google)?
Sign in with Google and approve access (OAuth). The connection also asks for: Default project. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Google Cloud (sign in with Google) without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the 2 that delete data ask first by default.
Can I use Google Cloud (sign in with Google) in workflows as well as agents?
Yes. Every Google Cloud (sign in with Google) action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Google Cloud (sign in with Google) to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.