Skip to main content
Version: Current

Activity Outputs

Overview​

The Activity Outputs drawer exposes output data produced by upstream activities in the workflow. It enables designers to directly reuse outputs from previously executed activities as inputs to subsequent activities, eliminating the need for explicit intermediate mapping.

While the references to activity outputs are configured at design time, the actual values are populated at runtime when the workflow instance executes.

What Appears in Activity Outputs​

The Activity Outputs drawer displays:

  • Only activities that expose output variables
  • One node per upstream activity in the execution flow
  • All output variables produced by each activity
  • Hierarchical structures for complex output types (objects and arrays)
note

The activity currently being configured is not displayed in the Activity Outputs drawer to prevent self-referencing.

Understanding Upstream Outputs​

Activity Outputs represent data produced by activities that logically precede the current activity in the workflow design.
These outputs become available for reference once the upstream activity completes during execution.

This ensures:

  • Clear execution order
  • Predictable data availability
  • Safe and type-consistent data flow

Simple Output Variables​

For activities that produce simple (primitive) outputs—such as strings, numbers, or booleans—the outputs are listed directly under the activity node.

Example:

  • Get Employee Info
    • EmployeeName
    • EmployeeID

Complex Output Variables​

For activities that produce complex outputs (objects or arrays), the drawer displays an expandable structure that mirrors the output schema.

The system uses a JSON schema representation to describe and expose nested properties.

Example:

  • Get Employee Info
    • Employee
      • firstName
      • lastName
      • address
      • designation

You can drag and drop:

  • The entire complex object, if the target input supports the same structure
  • An individual nested property, if the target input expects a compatible type

Using Activity Outputs (Drag & Drop)​

To use an activity output:

  1. Open the properties of the activity that requires input.
  2. Expand the Activity Outputs section in the Process Data drawer.
  3. Locate the upstream activity that produces the required output.
  4. Drag and drop the desired output variable into the target input field.

The designer automatically:

  • Inserts the correct reference
  • Validates type compatibility
  • Prevents invalid bindings

Liquid Expression Support​

Activity outputs are fully supported by the Liquid expression engine and can be referenced in expressions anywhere expressions are allowed.

Example:

If an activity named Get Customer Details exposes an output variable CustomerEmail, it can be referenced as:

{{ GetCustomerDetails.CustomerEmail }}