Skip to main content

SubWorkflow

Sub-Workflow Processor – Modular Workflow Orchestration​

Summary (SEO Meta Description):
The Sub-Workflow Processor in WeHub enables modular workflow design by allowing workflows to call other workflows and return results.
Available actions: Output and Invoke.

Overview​

The Sub-Workflow Processor allows you to break down complex processes into smaller, reusable workflows.
It provides two actions:

  • Invoke → Call another workflow from within the current workflow.
  • Output → Define and return values from a workflow for parent workflows to consume.

This processor is ideal for workflow modularity, reuse, and clean orchestration.

⚙️ Available Actions​

ActionDescription
InvokeRuns another published workflow inside the current workflow, synchronously returning results.
OutputDefines which values the Sub-Workflow should return to its parent workflow.

💡 Example Use Cases​

  • Healthcare → Invoke a Sub-Workflow that validates patient data, then return results to the main workflow.
  • Finance → Reuse a fraud detection Sub-Workflow across multiple transaction workflows.
  • Ops → Standardize logging, auditing, or notification flows by modularizing them.

FAQ​

Q: Can Sub-Workflows use schemas for inputs and outputs?
A: Yes, schemas ensure consistent structure when passing data between workflows.

Q: What happens if the Sub-Workflow fails?
A: The failure bubbles up to the parent workflow unless retries or error handling are configured.

Q: Can I reuse the same Sub-Workflow across projects?
A: Yes, as long as it is published and accessible in the environment.

Keywords: WeHub Sub-Workflow Processor, Invoke Workflow, Workflow Output, modular workflows, orchestration