List Keys
cloud_kms.list_keys
ActionGoogle Cloudconnection required
Calls Cloud KMS GET keyRings/{ring}/cryptoKeys.
List the crypto keys in a Cloud KMS key ring.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud KMS
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location, key_ring
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 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 |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location KMS location (overrides connection). | string | No | — | — | — |
key_ring Key ring id (overrides connection). | string | No | — | — | — |
page_size Max keys (1-1000). | number | No | 50 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_size": 50
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
keys | array | — |
count | number | — |
next_page_token | string | — |
{
"count": 0,
"keys": [],
"next_page_token": ""
}See List Keys run in a workflow.
In a technical demo we add the Google Cloud KMS connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.