Flow editor components

The Flow Builder comprises several major components:

• Toolbar: enables flow export, settings configuration, and testing capabilities.
• Settings: configure flow metadata and advanced options.
• Flow env variables: define flow-level constants accessible across all steps.
• Flow inputs: manage input parameters for the flow.
• Actions: individual steps that execute when the flow runs.
• Action editor: configure each action’s behavior.

Toolbar features

The toolbar provides access to:

• Summary: edit the flow’s title.
• Undo/Redo: navigate previous actions.
• Path: set permission levels.
• Menu options: deployment history, export as JSON/YAML, YAML editing.
• Tutorial access: guided walkthroughs with reset/skip options.
• Diff viewer: compare current state against the latest version.
• AI Builder: generate flows using artificial intelligence.
• Sticky notes: annotate the flow canvas.
• Test controls: run the full flow or test up to specific steps.
• Draft/Deploy: save or publish changes.

Settings configuration

Flow metadata includes:

• Summary: optional descriptive title.
• Path: unique identifier combining owner and flow name.
• Description: markdown-formatted instructions for users.
• Advanced options: worker group selection, caching, early stopping, return points, and shared directory access.

Flow environment variables

These flow-level constants are referenced using flow_env.VARIABLE_NAME syntax and support three types:

• String values (with optional workspace variable linking).
• JSON objects for structured data.
• Resource references resolved at runtime.

Flow inputs configuration

Three methods exist for adding inputs:

1. Customize manually: define name, type (Integer, Number, String, Boolean, Array, Object, Any), description, custom titles, and placeholders.
2. POST request: send a JSON payload to the capture endpoint for automatic field extraction.
3. Copy first step inputs: inherit inputs from the initial step.

Advanced settings vary by type and include currency formatting, regex patterns, file encoding, enum values, and resource type specifications.

Action steps

Steps can be created as:

• Inline scripts (Python 3.11, TypeScript/Deno, Go, Bash, Nu, SQL dialects, REST, GraphQL, PowerShell).
• References to scripts on the Orvanta Hub.
• References to workspace scripts.

Action editor components

The editor includes:

• Header: summary editing and shortcuts to retry, concurrency, cache, early stop, suspend, sleep, and mock configurations.
• Script editor: context variables, input variables, resources, reset, LSP assistant, formatting, and script viewing.
• Step configuration: input definition using templatable strings, dynamic expressions, or static values.
• Test section: isolated step testing with input configuration and result display.

Inputs accept three formats: templatable strings with ${variable} syntax, dynamic JavaScript expressions, or static values. Two insertion modes — append or connect — control how variables are added to inputs.