Get Bucket
gcs.get_bucket
ActionGoogle Cloudconnection required
Calls the GCS JSON API GET /b/{bucket}.
Read a bucket's location, labels, versioning, lifecycle and access config.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Storage
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- bucket
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 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 |
|---|---|---|---|---|---|
bucket Bucket name (overrides connection). | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
name | string | — |
location | string | — |
storage_class | string | — |
created | string | — |
id | string | — |
project_number | string | — |
location_type region / dual-region / multi-region. | string | — |
updated | string | — |
labels Bucket labels, e.g. the cost-centre tag. | object | — |
versioning Object versioning config ({'enabled': bool}). | object | — |
lifecycle Lifecycle rules, or absent when the bucket has none. | object | — |
retention_policy Retention period and lock state. | object | — |
iam_configuration Uniform bucket-level access and public-access prevention. | object | — |
encryption Default KMS key for new objects. | object | — |
logging | object | — |
website | object | — |
default_event_based_hold New objects are created on hold. | boolean | — |
etag | string | — |
self_link | string | — |
{
"created": "",
"default_event_based_hold": false,
"encryption": {},
"etag": "",
"iam_configuration": {},
"id": "",
"labels": {},
"lifecycle": {},
"location": "",
"location_type": "",
"logging": {},
"name": "",
"project_number": "",
"retention_policy": {},
"self_link": "",
"storage_class": "",
"updated": "",
"versioning": {},
"website": {}
}Related Google Cloud Storage nodes
See Get Bucket run in a workflow.
In a technical demo we add the Google Cloud Storage connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.