Overview#

Variables make workflows reusable. Instead of hardcoding values like email addresses or form data, you define variables in the workflow's inputs block and reference them in steps using template syntax.

Defining Variables#

Variables are declared in the inputs section of a RITSU workflow:

inputs:
  email:
    type: string
    label: 'Email Address'
    description: "The user's email for registration"
    required: true
  age:
    type: number
    label: 'Age'
    required: false
  acceptTerms:
    type: boolean
    label: 'Accept Terms'
    required: true

Each variable has:

Variable Types#

Scalar Types#

Composite Types#

Array#

A list of items. Use itemSchema to define the structure of each item.

inputs:
  users:
    type: array
    label: 'Users to register'
    required: true
    itemSchema:
      name:
        type: string
        label: 'Name'
      email:
        type: string
        label: 'Email'

Object#

A structured record with named properties.

inputs:
  address:
    type: object
    label: 'Shipping Address'
    required: true
    itemSchema:
      street:
        type: string
        label: 'Street'
      city:
        type: string
        label: 'City'
      zipCode:
        type: string
        label: 'ZIP Code'

Template Syntax#

Reference variables in step values using ${variableName} syntax.

Scalar References#

- id: step-1
  action: fill
  name: 'Enter email'
  mode: auto
  with:
    target:
      description: 'Email input field'
      vision:
        hint: "Text field labeled 'Email'"
    value: '${email}'

Object Property Access#

Use dot notation to access properties within an object variable:

value: "${address.street}"
value: "${address.city}"
value: "${address.zipCode}"

Array Item Access#

Use bracket-dot notation to reference properties within array items:

value: "${users[].name}"
value: "${users[].email}"

Variable Scope#

Where Templates Are Resolved#

Template expressions ${variableName} are supported in the following step fields:

Scope in Agent Steps#

Variables referenced in an agent step's prompt field are resolved before the agent starts. The agent receives a fully interpolated string and does not have access to the variable system during execution.

- id: step-3
  action: agent
  name: 'Fill dynamic form'
  with:
    prompt: 'Fill the registration form for ${name} with email ${email}'
    maxSteps: 10

In this example, ${name} and ${email} are replaced with their runtime values before the agent begins.

Resolution Timing#

Variables are resolved at execution time using the inputValues provided for each run. They are not resolved at workflow save time or during editing.

Variables in the Run Dialog#

When you run a workflow, the Run Workflow dialog presents input fields for each variable:

• Scalar variables — Rendered as text fields, number inputs, checkboxes, or date pickers based on type
• Required variables — Marked with a required indicator; the run cannot start until they are filled
• Descriptions — Displayed as helper text below each field

Variables in Batch Execution#

In batch mode, the input table has a column for each variable. Each row represents a separate run with its own set of values.

Each row is executed as an independent run within the batch.

Next Steps#