Public API: expose an endpoint to trigger an evaluation test run

Feature Requests Nodes
1

The problem
The public API (/api/v1) exposes evaluation test-runs as read-only:

  • GET /workflows/{id}/test-runs
  • GET /workflows/{id}/test-runs/{runId}
  • GET /workflows/{id}/test-runs/{runId}/test-cases

There is no endpoint to start a run. The only way to trigger one is the internal, undocumented POST /rest/workflows/{id}/test-runs/new — the same route the editor UI itself uses. Any CI/CD pipeline that wants to run n8n evaluations as part of an automated build has to depend on an internal API that can change shape without notice between releases, instead of the versioned, scoped public API.

What I’d like A public, versioned endpoint to trigger a test run for a workflows/{id}/test-runs, gated by an appropriate scope(workflow:execute, or a dedicated testRun:create/testRun:triggerscope similar to the existingtestRun:read/testRun:list). Response shape can mirror the internal endpoint's (a run id + initial status), so tady public (GET …/test-runs/{runId}) needs no changes. **Alternatives considered** Currently using the internal /rest` endpoint for triggering and the public API for polling results. This works, but it means the one step our CI pipeline can never fully decouple from n8n’s internal implementation is the mng a real workflow execution).

n8n version
Confirmed missing on 2.30.5 (verified against the live OpenAPI spec — no POST/PUT/PATCH exists anywhere near test-runs).