Google Cloud
Call Google Cloud APIs (Storage, BigQuery, Compute and more) with a service account key.
Connect it with: Service account. Google Cloud's own documentation: https://cloud.google.com/iam/docs/keys-create-delete.
What agents can do
Connect Google Cloud so the agents working your tasks can reach it. With it connected, they can:
- Read and write objects in Cloud Storage buckets a task names.
- Run BigQuery queries for a report.
- Read Cloud Logging entries and metrics to investigate an incident.
- Anything else the service account's roles allow, through gcloud or a client library.
Before you start
- A Google Cloud project, and permission to create service accounts and keys (Service Account Admin and Service Account Key Admin).
- The APIs agents use enabled in the project (APIs & Services > Library).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Google Cloud
Jaah connects to Google Cloud with a service account, not with a sign-in button.
Connect with an API key
Find each value first:
- Service account key: Google Cloud console > IAM & Admin > Service accounts > the account (or Create service account) > Keys > Add key > Create new key > JSON: paste the whole downloaded file.
- Project ID (optional): Leave blank to use the key's own project; otherwise the project ID from the console's project picker, such as acme-prod-123.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Google Cloud card.
- Name the secret and choose who can use it.
- Fill in Service account key, Project ID.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Google Cloud with a service account, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Google Cloud with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: service_account_json, project_id.
Tell the agent in your task description which secret to use, for example “use the Google Cloud secret org/gcp”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Google Cloud once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Google Cloud's side too, delete the service account's key in its cloud console.
Limitations
- Google Cloud has no sign-in button for apps like Jaah: you connect with a service account key.
- Many organizations block key creation with the iam.disableServiceAccountKeyCreation policy; an organization admin must allow it for the project.
- Agents get exactly the service account's roles: grant only what tasks need.
- Agents can do only what the connected Google Cloud service account and its roles allow.
Troubleshooting
Test says Google rejected the key (invalid_grant: Invalid JWT Signature)
The key was deleted or disabled. Create a new JSON key for the service account and select Replace.
Creating a key fails with Service account key creation is disabled
An organization policy blocks keys. Ask an organization admin to exempt the project from iam.disableServiceAccountKeyCreation.
Test passes but agents get PERMISSION_DENIED
The service account lacks a role. Grant it under IAM & Admin > IAM > Grant access.
Still stuck? Select Test and read the result: it names the value Google Cloud refused and the status it answered.
FAQ
Does Jaah store the whole key file?
Yes, encrypted. Only a signed assertion ever goes to Google; the private key itself never leaves Jaah's server during the test.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Google Cloud account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.