---
title: "Inclusive Gateway Split Node"
slug: "inclusive-gateway-split-node"
tags: ["workflow-builder", "workflow-builder-nodes"]
status: "update"
updated: 2026-10-13T15:36:31Z
published: 2026-10-13T15:36:31Z
canonical: "docs.unqork.io/inclusive-gateway-split-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.

# Inclusive Gateway Split Node

The Inclusive Gateway Split node routes the workflow down one or more paths simultaneously. All output links whose conditions are met execute in parallel—unlike the Exclusive Gateway node which only follows one. Pair with an Inclusive Gateway Join node to merge the paths back together. Use it when multiple conditions might be true at the same time and each matching path should run.

Unqork provides three gateway node types for branching paths:

- **Exclusive Gateway node**: Follows exactly one path—the first output link whose condition is met. Use for if/else logic.
- **Inclusive Gateway Split node**: Follows one or more paths—all output links whose conditions are met run in parallel. Use when multiple conditions might be true at the same time.
- **Parallel Gateway Split node**: Follows all paths simultaneously—no conditions required. Use when every branch must always run.

> **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 | `inclusive-gateway-split-{n}` | A display name for the node. |
| Error Message | `errorMessage` | Text input | — | The message displayed when no output link condition is met. |
| Links | — | — | — | Conditions are configured on the output links connecting from this node. All links whose conditions are met execute simultaneously. |

## Link Settings

When you click an output link connecting from this node, the settings panel displays settings specific to this link type. For the full reference, see [Output Links](/unqorkai/docs/output-links).

| Setting | Field | Type | Default | Description |
| --- | --- | --- | --- | --- |
| Label | `label` | Text input | — | A display name for the link. |
| Condition Formula | `formula` | Text input | — | The expression evaluated to determine whether the workflow follows this link. |
| Unidirectional | `uni` | Toggle | OFF | When set to **ON**, this setting lets the workflow proceed without waiting for this to complete. |
| Use Flash Message | `useFlashMessage` | Toggle | OFF | When set to **ON**, this setting displays a notification to end-users when the workflow follows this link. |
| ↳ Flash Message | `flashMessageText` | Text input | — | The notification message to display. Visible when **Use Flash Message** is **ON**. |
| ↳ Make Flash Message Dismissable | `flashMessageDismissable` | Checkbox | ☐ | When checked, this setting lets end-users dismiss the notification. Visible when **Use Flash Message** is **ON**. |
| ↳ Message Status | `flashMessageStatus` | Drop-down | — | The visual style of the notification. Options include: **Success**, **Info**, or **Danger**. Visible when **Use Flash Message** is **ON**. |

## Connection Rules

- The Inclusive Gateway Split node requires at least two output links.
- The workflow must contain an equal number of Inclusive Gateway Split and Inclusive Gateway Join nodes.
- All output paths must reach the same Inclusive Gateway Join node. Output paths cannot contain End nodes, Handoff nodes, Inclusive Gateway Split nodes, or Parallel Gateway Split nodes.
- Each node can only belong to one output path from an Inclusive Gateway Split node.
- Nodes outside the parallel process cannot connect to nodes inside it, and nodes inside cannot connect to nodes outside it.

---

**Changelog**

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

An app versioning Merge combines changes from one branch or draft, into another branch, draft, or published version of an application.

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.