Export Metadata Location
cloud_run.export_metadata_location
ActionGoogle Cloudconnection required
Calls run v2 GET /v2/projects/{projectsId}/locations/{locationsId}/{locationsId1}:exportMetadata.
Export generated customer metadata for a given resource.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Run
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, region
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 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 | — | — | — |
locations_id1 Locations id1 name or id. | string | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
metadata | string | — |
{
"metadata": ""
}Related Google Cloud Run nodes
See Export Metadata Location run in a workflow.
In a technical demo we add the Google Cloud Run connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.