Integrating Google Cloud Secret Manager
Bruno integrates with Google Cloud Secret Manager to securely fetch secrets for use in your collections. The provider is configured once in Preferences and can then be attached to any collection environment.
Configuration steps
- Go to Preferences and open the Secrets Manager section from left-bottom sidebar.
- Click + Add Secret Manager.
- Select GCP Secrets Manager as the provider type.
- Enter a Name for the account (for example,
Production GCP). -
Provide your service account credentials using either method:
-
Upload or paste a GCP service account JSON key - Bruno fills in Default Project ID, Client Email, and Private Key from the file.
-
Or enter the fields manually:
- Default Project ID - defaults from the key’s
project_id, you can change it later per environment when fetching secrets - Client Email - for example,
service-account@project.iam.gserviceaccount.com - Private Key - the
private_keyvalue from the service account JSON
- Default Project ID - defaults from the key’s
-
Click Test Connection to verify that Bruno can authenticate with the service account.
- Click Add (or Save when editing) to save the secret manager configuration.

Once saved, the account appears in the Secrets Manager list and is available when configuring external secrets on an environment.
gcloud CLI authentication, and Workload Identity Federation are planned for future support. Use a service account key for now.
Exporting as a .env file
Once a provider is saved, you can export its configuration as a .env file from Preferences > Secrets Manager. This is useful for passing credentials to the Bruno CLI or seeding a CI/CD pipeline.
- In the Secrets Manager list, hover over the account you want to export.
- Click the Export as .env icon.
- Bruno writes the credentials to a
.envfile on your machine.

The exported file includes variables such as:
BRUNO_GCP_SECRETS_MANAGER_PROJECT_ID=my-project
BRUNO_GCP_SECRETS_MANAGER_CLIENT_EMAIL=service-account@my-project.iam.gserviceaccount.com
BRUNO_GCP_SECRETS_MANAGER_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n"
.env file contains your service account private key in plain text. Add it to .gitignore immediately and never commit it to version control.
Pass the exported file to the CLI using the --secrets-env-file flag:
bru run collection/ --env Production --secrets-env-file ./secrets.env
Next steps
- Configure and fetch secrets — attach the provider to an environment and pull secrets into Bruno
- Use secrets in requests — reference fetched secrets in headers, body, auth fields, and scripts