Changelog
Google Secret Manager, and keys you paste go to the Vault
Google Secret Manager is now an integration, and your agent can turn the keys stored there into connections. Ask it to bring over your Stripe, OpenAI, or HubSpot keys and it lists the secret names in your project, then has General Input read the ones you name, check each against its service, and save it to the Vault. The values themselves never pass through the conversation. When you paste an API key into a chat instead, the agent saves that to the Vault the same way.
How it works
- Least privilege by default. The setup guide has you create a service account that may read only the secrets you pick, plus see the list of secret names. Your agent lists names, labels, and versions, and your Agent Firewall rules for Secret Manager apply to every call, including the reads made to save a key.
- Every API-key integration, built-in or custom. A save checks the fields each integration expects and tests the key with the service, the same check a connection made by hand gets. A key that fails is reported and never saved.
- A copy, not a link. Changing a secret later doesn't change the connection. Save it again onto the same connection to rotate its key, and everything using it keeps working.
- Answers that never repeat a key. A save answers with the new connection's name and id, or why it failed, in fixed words that never quote a key or the secret it came from.
- Only from your own chats. Keys are saved from your own conversations and the MCP connector. Workflow runs, test runs, apps, and scripts can't save them.