Get Run
currents.get_run
ActionBusiness appsconnection required
Calls the Currents API with the connection's credentials.
Fetch one run with its groups, spec files and test totals.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Currents
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 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 |
|---|---|---|---|---|---|
run_id Identifier of the run to act on, as returned by currents.list_project_runs. | string | Yes | — | — | cGxheXdyaWdodC1ydW4tMQ |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"run_id": "cGxheXdyaWdodC1ydW4tMQ"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
runId Identifier of the run. | string | — |
projectId Project the run belongs to. | string | — |
status Current verdict of the run, such as PASSED or FAILED. | string | — |
completionState Whether the run is COMPLETE, IN_PROGRESS or CANCELED. | string | — |
createdAt ISO-8601 timestamp of when the run started reporting. | string | — |
completedAt ISO-8601 timestamp of when the run finished, if it has. | string | — |
tags Tags the run was reported with. | array | — |
meta Commit, branch and CI metadata Currents recorded for the run. | object | — |
groups The run's groups, one per parallel configuration. | array | — |
specs One entry per spec file, with its instance id and results. | array | — |
{
"completedAt": "",
"completionState": "",
"createdAt": "",
"groups": [],
"meta": {},
"projectId": "",
"runId": "",
"specs": [],
"status": "",
"tags": []
}See Get Run run in a workflow.
In a technical demo we add the Currents connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.