SubWorkflowInvoke
Sub-Workflow – Invoke
Summary (SEO Meta Description):
The Sub-Workflow Invoke action in WeHub runs another workflow inside the current workflow.
Configure which Sub-Workflow to call and reuse modular workflow logic.
Overview
The Invoke action allows you to call a separate Sub-Workflow from within your main workflow.
This makes workflows modular, reusable, and easier to manage by breaking down complex processes into smaller units.
When invoked, the Sub-Workflow runs as part of the current workflow and can return outputs via the Output action.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Invoke Patient Validation"). |
| Sub Workflow | Workflow | Select which published Sub-Workflow to invoke. |
💡 Example Use Cases
- Healthcare → Invoke a reusable Sub-Workflow for patient validation.
- Finance → Run a Sub-Workflow for fraud detection inside the main payment workflow.
- Ops → Call standard workflows (logging, auditing, notifications) as modular steps.
FAQ
Q: Can I pass inputs to the Sub-Workflow?
A: Yes, use the schema-based input/output configuration when defining the Sub-Workflow.
Q: What happens if the Sub-Workflow fails?
A: The failure propagates to the parent workflow unless error handling or retries are configured.
Q: Does Invoke wait for the Sub-Workflow to finish?
A: Yes, it executes synchronously and returns results before continuing.
Keywords: WeHub Sub-Workflow, Invoke Workflow, workflow orchestration, modular automation, reuse