Add Version
secret_manager.add_version
ActionGoogle Cloudconnection required
Calls POST /projects/{project}/secrets/{secret}:addVersion with a base64 payload.
Add a new version (value) to an existing Secret Manager secret.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Secret Manager
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
secret_id Secret id (short name). | string | Yes | — | — | — |
value Secret value (plaintext). | string | Yes | — | credential material | credential |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
name | string | — |
secret_id | string | — |
version | string | — |
state | string | — |
{
"name": "",
"ok": false,
"secret_id": "",
"state": "",
"version": ""
}Related Google Secret Manager nodes
See Add Version run in a workflow.
In a technical demo we add the Google Secret Manager connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.