Get Instance
currents.get_instance
ActionBusiness appsconnection required
Calls the Currents API with the connection's credentials.
Fetch one spec file's execution, with every test result it recorded.
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 |
|---|---|---|---|---|---|
instance_id Identifier of the spec-file execution, from a run's 'specs' entries. | string | Yes | — | — | aW5zdGFuY2UtMQ |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"instance_id": "aW5zdGFuY2UtMQ"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
instanceId Identifier of this spec-file execution. | string | — |
runId The run the instance belongs to. | string | — |
groupId The run group the instance was executed in. | string | — |
spec Path of the spec file that was executed. | string | — |
machineId The machine that claimed the spec file. | string | — |
claimedAt ISO-8601 timestamp of when execution started. | string | — |
completedAt ISO-8601 timestamp of when it finished. | string | — |
results Stats, exception and per-test results. | object | — |
{
"claimedAt": "",
"completedAt": "",
"groupId": "",
"instanceId": "",
"machineId": "",
"results": {},
"runId": "",
"spec": ""
}Related Currents nodes
See Get Instance 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.