Login
Free Sign Up
Docs
/

Flow - Result

Type identifier: flow:result Category: Flow Operations

Description

Returns a result value from a Flow run. The result is made available to the caller when the Flow completes. A Flow can have multiple result nodes for different run paths.

Input Handles

Handle

Data Type

Required

Description

trigger

trigger

Yes

Execution trigger input

result

Varies

Yes

The value to return from the Flow

Input Handle Details

result

  • Type: Configurable via result.type — can be any schema type
  • Notes:

    • When unconnected, defaults to any type and auto-detects when connected
    • Accepts values such as Records, strings, numbers, booleans, objects, arrays, files, and content

Output Handles

This node has no output handles. It ends the path of the run.

Configuration Options

Property

Type

Required

Default

Description

label

string

Yes

"Flow - Result"

Display label for the node

result

object

Yes

Any type (type: null)

Configuration for the result value

Configuration Details

result

  • Type: object with id (string) and type; type is null or one of: entity, string, number, boolean, date, duration, file, object, geojson, array, content
  • Default:

    {
      "id": "<generated>",
      "type": null
    }
  • Notes:

    • When type is null, the handle accepts any type and auto-configures on connection
    • The name property within the type controls the handle label

Behaviour

Execution Flow

  1. Node receives trigger on the trigger input handle
  2. Resolves the value connected to the result input handle
  3. Maps the value to the configured Schema type
  4. Converts ID-based Record references to name-based format
  5. Sets the result as the run output

Result Processing

The result value undergoes the following transformations:

  1. Schema Mapping: Value is mapped to match the configured result.type Schema
  2. Record Conversion: If the value is a Record with ID-based property references, it is converted to name-based format for readability

Flow Output

The processed result is:

  • Returned as the run output
  • Available to the caller through the API that reads run outputs

Edge Cases

Scenario

Behaviour

No value connected

Result is undefined

Type mismatch

Value is mapped/coerced to target Schema

Record with ID references

Converted to name-based property references

Multiple result nodes

First triggered result node provides output

Examples

Basic String Result

{
  "type": "flow:result",
  "data": {
    "label": "Flow - Result",
    "result": {
      "id": "res1",
      "type": {
        "type": "string",
        "name": "Message",
        "display": "text"
      }
    }
  }
}

Input Handles:

  • trigger (trigger)
  • result (string)

Record Result

{
  "type": "flow:result",
  "data": {
    "label": "Return Contact",
    "result": {
      "id": "res1",
      "type": {
        "type": "entity",
        "schemaId": "clx1234567890abcdefghij",
        "name": "Contact"
      }
    }
  }
}

Input Handles:

  • trigger (trigger)
  • result (entity matching schemaId)

Object Result

{
  "type": "flow:result",
  "data": {
    "label": "Return Summary",
    "result": {
      "id": "res1",
      "type": {
        "type": "object",
        "name": "Summary",
        "properties": {
          "total": { "type": "number", "name": "Total" },
          "items": { "type": "array", "name": "Items", "items": { "type": "string" } }
        }
      }
    }
  }
}