SubWorkflowOutput
Sub-Workflow – Output
Summary (SEO Meta Description):
The Sub-Workflow Output action in WeHub saves the results of a workflow for use in parent workflows.
Configure output fields with names, paths, and types to return structured data.
Overview
The Output action defines which values a workflow will expose when invoked as a Sub-Workflow.
By mapping workflow context fields to named outputs, you can make results available to parent workflows or downstream consumers.
This ensures clean, reusable workflow modules with well-defined outputs.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Return Patient Data"). |
| Name | String | Name of the output field. |
| Path | String | Path in the workflow context where the output value is located. |
| Type | Enum | Data type of the output. Options: NUMBER, STRING, BYTE, DATE, DATETIME, BOOLEAN, OBJECT, ARRAY, ANY. |
| Using Schema for Outputs/Inputs | Boolean | Toggle to enforce schema validation on outputs/inputs. |
| Schema | Schema | (Optional) Select a schema to validate output structure. |
| Truncate Fields | Boolean | If enabled, truncates large fields. |
| Truncate Level | Integer | Depth/length limit applied when truncation is enabled. |
💡 Example Use Cases
- Healthcare → Return a staged
PatientFHIR resource from a Sub-Workflow. - Finance → Output normalized
Transactionobjects for reporting. - Ops → Provide workflow execution results (logs, flags, IDs) back to parent workflows.
FAQ
Q: Can I define multiple outputs?
A: Yes, add multiple rows to return multiple fields.
Q: What happens if a path is invalid?
A: The output will be null unless a default or schema rule enforces a value.
Q: Is schema validation required?
A: No, but recommended for consistency when reusing Sub-Workflows.
Keywords: WeHub Sub-Workflow, Workflow Output, return values, schema validation, modular workflows