Editor overview
The Orvanta editor is where you build and inspect automation. It is visual-first: you compose workflows on a node-based canvas, but everything you build is backed by a deterministic code artifact.
The editor has three complementary surfaces:
| Surface | What you build |
|---|---|
| Workflow editor | Node-based canvas for wiring steps into a flow. |
| Script editor | A focused code editor for individual scripts, with instant testing. |
| App editor | Build internal UIs and forms on top of your scripts and workflows. |
The workflow canvas
Section titled “The workflow canvas”The canvas shows your workflow as a graph of nodes connected by edges. For each node you can:
- choose its type (script, approval, condition, webhook, delay, sub-workflow),
- set its inputs — referencing trigger data, variables, resources, or the outputs of earlier nodes,
- and inspect its output after a run.
Instant preview and testing
Section titled “Instant preview and testing”You don’t have to deploy to see results. Run a single node or the whole workflow from the editor and watch outputs appear inline, node by node. Inputs are validated against the declared schema before execution, and any auto-generated UI is available to drive test runs.
From canvas to code and back
Section titled “From canvas to code and back”Because the artifact is the source of truth, you can switch a workflow to its code representation, edit it, and switch back — or export it for review in Git. See Workflows as code.