Step Output

1. What Is a Step Output?

A step output is the structured data returned by a node earlier in the workflow. Common examples:

• A trigger (e.g. “Record Created in Supabase”)

• A lookup or query step (e.g. “Find Contact by Email”)

• A custom script or API request

Each output contains objects and fields that can be referenced by components inside the Build Any UI node.

2. How Components Receive Data

Each component in the UI editor supports default values and runtime bindings. These values are set using step outputs.

Examples:

• Pre-filling a Text Input with Step 2 > user > name

• Showing a company logo in an Image component using Step 1 > organization > logo_url

• Displaying a list of options in a Select or Checkbox from Step 3 > planOptions

These bindings can be applied to:

• Default values

• Labels and descriptions

• Visibility rules

• Placeholders or tooltips

3. Anatomy of a Data Reference

When you apply data to a component, the reference appears as a step output pill, containing:

• The step number where the data came from

• The type of object (e.g. Contact, Row, JSON, Email)

• The field name being referenced (e.g. email, company.name)

• Nested fields via dot notation (e.g. customer.account.region)

You can always trace the origin of the value by inspecting the label on the reference.

4. Linked and Nested Data Support

All MergePoint step outputs support linked object traversal, meaning you don’t need additional steps to access nested fields.

For example:

• Invoice > line_items[0] > product.name

• Contact > company > owner > email

If the structure exists in the upstream step’s output, it’s directly accessible.

5. Live Evaluation at Runtime

All referenced values are evaluated live during the workflow run. This means:

• You don’t need to refresh or re-fetch data later in the flow

• Even if the workflow pauses (e.g. after a wait or manual review), the data stays current

• Components always render the latest available value from the originating step

6. Type Awareness in Components

Components enforce value compatibility:

• Date pickers only accept values typed as Date

• Select components require arrays or strings depending on the mode

• Files or Images must come from a File-type field or URL

If the data type mismatches the component, the UI will alert you or fallback to static input.

7. How to Apply Data in the UI Editor

When configuring any component inside the Build Any UI node:

To bind a value:

• Click the “Default Value” or relevant field

• Choose “Insert from Step”

• Select the value from the dynamic picker
  (or press @ to open inline during text editing)

Supported Fields for Binding:

• Default values (input, number, select, etc.)

• Static text (labels, help descriptions)

• Visibility conditions

• Conditional display logic (e.g. show section if status = 'Pending')

8. Inspecting Available Outputs

To see which data you can bind:

1. Open the step settings of any previous node

2. Navigate to the “Output” tab

3. Expand fields to see all objects and nested values

4. Hover to view data types and sample values

This allows you to bind with confidence and avoid type mismatches.

Summary