Flow - Result
Type identifier:
flow:resultCategory: 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 |
|---|---|---|---|
| Varies | Yes | The value to return from the Flow |
Older Flows may still connect a control output to a trigger input on this node. The designer shows that Trigger handle only while such a connection exists, and the Flow saves with it. Remove the connection to remove the handle.
Input Handle Details
result
- Type: Configurable via
result.type— can be any schema type Notes:
- When unconnected, defaults to
anytype and auto-detects when connected - Accepts values such as Records, strings, numbers, booleans, objects, arrays, files, and content
- When unconnected, defaults to
Output Handles
This node has no output handles. It ends the path of the run.
Configuration Options
Property | Type | Required | Default | Description |
|---|---|---|---|---|
|
| Yes |
| Display label for the node |
| object | Yes | Any type ( | Configuration for the result value |
Configuration Details
result
- Type: object with
id(string) andtype;typeisnullor one of:entity,string,number,boolean,date,duration,file,object,geojson,array,content Default:
{ "id": "<generated>", "type": null }Notes:
- When
typeisnull, the handle accepts any type and auto-configures on connection - The
nameproperty within the type controls the handle label
- When
Behaviour
Execution Flow
- Resolves the value connected to the
resultinput handle - Maps the value to the configured Schema type
- Converts ID-based Record references to name-based format
- Sets the result as the run output
Result Processing
The result value undergoes the following transformations:
- Schema Mapping: Value is mapped to match the configured
result.typeSchema - Record Conversion: If the value is a Record with ID-based property references, it is converted to name-based format for readability
Values marked sensitive cannot be returned as the top-level Flow run result; the result node fails if a sensitive value is connected at that boundary. This includes wrapped values from Secret - Get and plaintext from Secret - Unwrap.
In Flows v2, sensitive values may be returned from an inline child Flow to its calling Flow - Execute node. They retain their sensitivity and cannot be returned as the top-level Flow run result. This restriction also applies to nested sensitive fields and list items. Wrapped Secret Values remain disallowed even in child Flow results. An unmarked sibling selected with Object - Pick may be returned when neither that field nor an ancestor is sensitive. Run inspection shows trait labels and paths, not sensitive payloads.
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 |
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:
result(string)
Record Result
{
"type": "flow:result",
"data": {
"label": "Return Contact",
"result": {
"id": "res1",
"type": {
"type": "entity",
"schemaId": "clx1234567890abcdefghij",
"name": "Contact"
}
}
}
}Input Handles:
result(entitymatchingschemaId)
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" } }
}
}
}
}
}