Currents
Read and control Cypress, Playwright and Jest test runs recorded by Currents (currents.dev).
OCNORA ships 8 typed Currents operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.currents.dev/v1 through the HTTP node with the same credential.
Before you connect Currents
- Authentication
- Bearer token
- Credential
- the API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The key needs Currents' webhooks:read and webhooks:write scopes — a read-only key lists runs happily and still fails to publish. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Currents can reach.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Currents
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Read and search 6
Delete and cancel 2
A sample Currents workflow
- 1Run Eventtrigger.currents_eventStart a run when a Currents CI test run starts, finishes, times out or is cancelled.
- 2Find Runcurrents.find_runFind 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.
- 3Cancel Runcurrents.cancel_runCancel a run that is still executing so its machines stop early.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Cancel RunCancel a run that is still executing so its machines stop early.currents.cancel_run
- Delete RunDelete a run and the results recorded against it.currents.delete_run
- Find RunFind 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.currents.find_run
- Get InstanceFetch one spec file's execution, with every test result it recorded.currents.get_instance
- Get ProjectFetch one project's settings, including its run timeouts.currents.get_project
- Get RunFetch one run with its groups, spec files and test totals.currents.get_run
- List Project RunsList a project's recent test runs, filtered by branch, tag or status.currents.list_project_runs
- List ProjectsList the organisation's Currents projects, one cursor page at a time.currents.list_projects
Currents questions
- How does OCNORA authenticate with Currents?
- With a stored Bearer token credential, shaped the API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Currents?
- 8 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Currents operation I need is not listed?
- Call https://api.currents.dev/v1 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Currents?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Currents calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Currents workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.