Skip to main content
The Workflow Editor ships with a built-in test panel. Use it to validate a draft against a known input before promoting to active.

​
Three test modes

Paste one input payload. The engine runs the graph end-to-end and shows per-node output in the right pane. No decision is committed.

​
What the test pane shows

Per node:
  • Status — completed / skipped / errored / timed_out.
  • Elapsed — milliseconds.
  • Input — the run-context slice the node consumed.
  • Output — what it wrote back.
Per run:
  • Path — sequence of node ids the engine traversed.
  • Terminal output — the final state.
  • Decision payload — what would have been written if this weren’t a test run.

​
Mocking vendor responses

For workflows that talk to expensive or slow vendors (Crystal, BigDataCorp), the test pane supports a mocks map: 
{
  "mocks": {
    "<node-id>": {
      "output": {
        "sanctions_hit": false,
        "pep_hit": false,
        "match_score": 0,
        "risk_level": "low"
      }
    }
  }
}
The engine replaces the node’s actual vendor call with the mock. Useful for testing the post-vendor branches without burning quota, or for reproducing a specific vendor response while iterating on downstream logic.