List Runs
data_lineage.list_runs
ActionGoogle Cloudconnection required
Calls Data Lineage GET /v1/projects/{projectsId}/locations/{locationsId}/processes/{processesId}/runs.
Lists runs in the given project and location. List order is descending by start_time.
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
5 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 |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location / region (overrides connection). | string | No | — | — | — |
process Id of the process to act on, from data_lineage.list_processes — not its name. | string | Yes | — | — | — |
page_size Optional. The maximum number of runs to return. The service may return fewer than this value. | number | No | 50 | ≥ 1 | — |
page_token Optional. The page token received from a previous `ListRuns` call. Specify it to get the next page. When pagin | string | No | — | — | — |
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 |
|---|---|---|
ok | boolean | — |
runs | array | — |
nextPageToken | string | — |
{
"nextPageToken": "",
"ok": false,
"runs": []
}Related Google Data Lineage nodes
See List Runs 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.