Sub Workflow

Published Workflows expose reusable automation behind a stable Workflow key. They let other Workflows call shared logic instead of duplicating the same Steps.

The Sub Workflow Node calls a published V1 or V2 Workflow from the current Workflow. Use it for shared validation or a reusable child process with its own published Parameters and Returns.

Revision History

0.0.0.14 - Current release, including support for published V1 and V2 Workflows.
0.0.0.8 - Initial release.
0.0.0.9 - Improved returns to remove Result root object.

Setup Notes

The target Workflow must be published before you can select it. Ensure that it exposes the Parameters and returns that you want to use before publishing it.

When you select a V2 Workflow, the Node surfaces its published Parameter and return schema. For a V1 Workflow, the Node surfaces the applicable Variable Bar inputs and outputs and adds (v1) to the template name.

For broader guidance on structuring reusable Workflows, see How to use Sub Workflows.

Methods

The Sub Workflow Node exposes one method.

CallWorkflow

Invokes the published V1 or V2 Workflow identified by WorkflowKey.

Parameter	Type	Description
WorkflowKey	String	The Workflow key of the published Workflow to call.

The method exposes each published return from the target Workflow directly, without a Result wrapper. The return names and types therefore depend on the selected Workflow. If the target Workflow has no published returns, the Node does not expose any return fields.

Usage Notes

• If you only provide a WorkflowKey, the Node can still call the target Workflow, but the design-time schema is more useful when the target Workflow has published parameters and returns.
• Publish the target Workflow again after changing its Parameters or returns so that the selectable template reflects the updated schema.