Auto-generated UIs

When a script or workflow declares its inputs, Orvanta automatically generates a form to collect those inputs — no front-end code required. The form is derived from the input schema, so it stays in sync with the code.

How it works

A script’s inputs are inferred from the parameters of its main function. From the signature, Orvanta infers:

• the fields to render,
• their types (string, number, boolean, object, …),
• which are required,
• and any default values.

def main(customer_id: str, dry_run: bool = False):
    ...

The example above renders a required text field for customer_id and a checkbox for dry_run that defaults to off.

Type-to-control mapping

Declared type	Rendered control
string	Text input
string with enum	Dropdown
boolean	Checkbox
number	Number input
object	JSON editor

Why it matters

Auto-generated UIs mean any script becomes a self-service tool the moment it’s published — non-technical teammates can run it safely, with validation handled before execution. Because the form comes from the schema, there’s no separate UI to maintain when the inputs change.

Related

• Scripts — Declaring inputs and outputs.
• Triggers — How inputs are passed when a run starts.
• Editor overview — Where forms are surfaced.