List Secrets Locations
secret_manager.list_secrets_locations
ActionGoogle Cloudconnection required
Calls secretmanager v1 GET /v1/projects/{projectsId}/locations/{locationsId}/secrets.
Lists Secrets.
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, none 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 |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
filter Server-side filter expression; blank returns everything. | string | No | — | — | — |
page_token The previous response's nextPageToken; blank = first page. | string | No | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
nextPageToken | string | — |
secrets | array | — |
totalSize | integer | — |
{
"nextPageToken": "",
"secrets": [],
"totalSize": 0
}Related Google Secret Manager nodes
See List Secrets Locations 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.