Quick Answer: What is a Sub-Workflow Node?

[!NOTE] The Sub-Workflow Node allows you to "call" one workflow from inside another. Instead of building a massive, unmanageable 50-node diagram, you can break your logic into small, reusable pieces (e.g., a "GDPR Anonymizer" sub-workflow) and trigger them whenever needed within your main pipelines.

Core Capabilities

1. Reusable Logic Components

Create a single workflow that "Signs and Watermarks a PDF". Instead of recreating these 4 nodes in every new project, simply drag the Sub-Workflow node into any canvas and select your "Signature Engine" draft.

2. Standardized Branding

Maintain a "Header/Footer" sub-workflow that adds your company's official branding to any document. If your logo changes, you only need to update the sub-workflow once to fix every pipeline in your account.

3. Parallel Batch Handling

Use a Sub-Workflow inside a Loop Node. This allows you to execute complex, multi-step logic for every item in a list without cluttering the main canvas, making it much easier to debug and scale.

Configuration Guide

Field	Description	Requirement
Workflow ID	The specific draft or template to execute.	Mandatory
Input Map	Map parent variables to sub-workflow triggers.	Recommended
Await Result	Wait for the sub-workflow to finish before continuing.	Default: True

Best Practices

Stateless Sub-Workflows: Design your components to be stateless—they should take an input, process it, and return an output without relying on external global variables.
Naming Conventions: Name your sub-workflows clearly (e.g., Helper: OCR Extraction) so your team can quickly identify each workflow's purpose.

[!TIP] Returning specific data? Use the specialized Workflow Output Node inside your sub-workflow to explicitly define what the parent workflow receives.