---
title: "Sub-Process Node"
slug: "sub-process-node"
tags: ["workflow-builder", "workflow-builder-nodes"]
status: "update"
updated: 2026-10-13T15:37:24Z
published: 2026-10-13T15:37:24Z
canonical: "docs.unqork.io/sub-process-node"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sub-Process Node

The Sub-Process node groups a set of nodes into a collapsible, reusable container in the workflow canvas. It can only be placed in the Authenticated swimlane. Use it to organize complex workflows into logical sections and to define role-based swimlanes for access control.

Add a node to it by dragging a Task node **onto the Sub-Process node** — the container grows to hold it, and the task takes on the sub-process's swimlane and task type. Drag a nested task back onto a swimlane to remove it from the container.

> **How to read settings tables**
> 
> 
> The tables below describe each configurable option as it displays in the UnqorkAI platform. Values are formatted as follows: `inline code` — a value to type exactly as shown | **Bold** — a value selected from a drop-down, radio button, tab, or choice chip | **ON**/**OFF** — toggle state | ✓ — checkbox checked | ☐ — checkbox unchecked

## Settings

| Setting | Field | Type | Default | Description |
| --- | --- | --- | --- | --- |
| Label | `label` | Text input | `subprocess-{n}` | A display name for the node. Supports template expressions (for example, `subprocess-{{ data.number }}`). |
| Allow Navigation with Errors | `allowNavigationWithErrors` | Toggle | OFF | When set to **ON**, this setting lets end-users navigate forward even when validation errors are present. |
| Validate When Leaving Sub-Process | `validateOnLeavingGroup` | Toggle | OFF | When set to **ON**, this setting validates all fields when an end-user exits the subprocess. |

## Placement Constraints

- The Sub-Process node can only be placed in the **Authenticated swimlane**. It cannot be placed in an Automated swimlane.
- Only **Task nodes** can be nested inside a Sub-Process node. A Sub-Process node cannot contain another Sub-Process node.
- Any links already connected to a task are **removed** when you drag it into a Sub-Process node. Nested tasks run in left-to-right order inside the container, so their sequence comes from their position rather than from links you draw.
- A task carrying a boundary event — an [Error](/unqorkai/docs/error-node), [Timed Event](/unqorkai/docs/timed-event-node), or [Conditional Event](/unqorkai/docs/conditional-event-node) node — is refused. Remove the attached event first, then drag the task in.

---

**Changelog**

| Date | Change |
| --- | --- |
| — | Initial publication. |

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.