Get Run

data_lineage.get_run
ActionGoogle Cloudconnection required

Calls Data Lineage GET /v1/projects/{projectsId}/locations/{locationsId}/processes/{processesId}/runs/{runsId}.

Gets the details of the specified run.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Data Lineage
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
process
Id of the process to act on, from data_lineage.list_processes — not its name.
stringYes———
run
Id of the run to act on, from data_lineage.list_runs — not its name.
stringYes———

Output

One shape.

result

FieldTypeExample
ok
boolean—
name
string—
attributes
object—
endTime
string—
state
string—
displayName
string—
startTime
string—
{
  "attributes": {},
  "displayName": "",
  "endTime": "",
  "name": "",
  "ok": false,
  "startTime": "",
  "state": ""
}

See Get Run run in a workflow.

In a technical demo we add the Google Data Lineage connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.