Find Run

currents.find_run
ActionBusiness appsconnection required

Calls the Currents API with the connection's credentials.

Find the most recent completed run for a CI build id or a branch, which is how a workflow picks up the run its own pipeline just produced.

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

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

FieldTypeRequiredDefaultConstraintsExample
project_id
Currents project to act on; overrides the default project on the connection.
stringNo——abc123
ci_build_id
The CI build id the run was reported under, such as a GitHub run id.
stringNo——17482930212
branch
Git branch the run was reported from; a trailing * matches by prefix.
stringNo——release/*
tags
Only consider runs carrying these tags, as a JSON array or a comma-separated list.
arrayNo—array of string["nightly"]
pw_last_run
Return Playwright's last-run summary for the matched run so a rerun can target only the failed tests.
booleanNofalse——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "branch": "release/*",
  "ci_build_id": "17482930212",
  "project_id": "abc123",
  "pw_last_run": false,
  "tags": [
    "nightly"
  ]
}

Output

One shape.

result

FieldTypeExample
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 Find 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.