---
title: "Conditional Event Node"
slug: "conditional-event-node"
updated: 2025-12-23T15:23:31Z
published: 2025-12-23T15:23:31Z
canonical: "docs.unqork.io/conditional-event-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.

# Conditional Event Node

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional_Event_Node_Intro.webm?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)

The **Conditional Event node** uses logic to redirect a [workflow](/v1/docs/introduction-to-workflow) that's currently in a [Sub-Process](/v1/docs/sub-process-node) node. The conditional logic specified in the Conditional Event node's outgoing link checks for data collected in the Sub-Process node. If the data matches the logic check's parameters, it directs the workflow out of the Sub-Process node and to the linked node.

The Conditional Event node checks logic at these points in a Sub-Process workflow:

- Beginning of the Sub-Process.
- End of each task in the Sub-Process.
- End of the Sub-Process.

Each Sub-Process node can only contain one Conditional Event node. The Conditional Event node includes one output port that links to a single node outside of the Sub-Process node. The Conditional Event node's Output link contains the logic used to trigger the node.

## Similar Logic Nodes

While the following nodes have similar functions, the Conditional Event node is different from Gateway nodes in the following ways:

- **Conditional Event node**: Uses conditional logic to redirect a workflow from a Sub-Process node to another path.
- [**Exclusive Gateway node**](/v1/docs/exclusive-gateway-node): Uses conditional logic to redirect a workflow to one or more paths outside a Sub-Process node.
- [**Inclusive Gateway node**](/v1/docs/inclusive-gateway-split-node): Uses conditional logic to redirect a workflow to one or more paths outside a Sub-Process node.

## Settings Menu Description

Let's explore the node's **Settings Menu**. This menu displays as a blue menu bar, either above or below the node, when you select the node itself. This node has these Settings Menu options:

| **Setting** | Description |
| --- | --- |
| **Edit** | Opens the Edit Conditional Event window, where you can configure related settings. |
| **Delete** | Removes the Conditional Event node from the Sub-Process. |

### Edit Conditional Event Window Description

Click the **Edit** button to display the **Edit Conditional Event** window.

![A static image displaying the Conditional Event Node and the Edit Conditional Event Settings window.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional_Event_Node_Settings.jpg?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)

| **Setting** | Description |
| --- | --- |
| **Label** | The name of your node. By default, the Label displays as `conditionalEvent-1`. The label you enter here is optional and displays below the node on the workflow canvas. Define your labels by associating them with the role of the node. |
| **Output Links** | Displays the logic and linked node for each path from the Conditional Event node. You can edit each item from here. |
| **X (Close)** | Closes the Edit Conditional Event window. |

### Conditional Event Links Settings Menu

Selecting the Conditional Event link opens a **Settings Menu**. This menu displays as a blue menu bar above the link indicator. The menu has the following options:

| **Setting** | Description |
| --- | --- |
| **Edit** | Opens the Edit Conditional Event Link window. From there, you can configure settings relating to the Conditional Event link. |
| **Delete** | Removes the link from the workflow. |

### Edit Conditional Event Link Window Description

Clicking the **Edit** button displays the **Edit Conditional Event Link** window.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional_Event_Node_Link_Description.webm?&sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)

| **Setting** | Description |
| --- | --- |
| **Label** | The name applied to the link. This label is optional and displays below the link once set. Labels should be user-friendly and well-associated with the role of the node. |
| **Status** | You can enter a text value here. Other components can query the Status value of a link. When the workflow passes the link, the Status value populates with the Status field text. |
| **Logic** | Sets the logic for the Conditional Event node link. The Conditional Event link icon changes from ![unlinked](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Unlinked_Workflow.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) (unlinked) to ![linked](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Linked_Workflow.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) (linked) when logic is present. The expression typically consists of a Property ID, an operator, and criteria (value) for matching. For example: - `propertyId='string'` - `propertyId>100` - `propertyId=TRUE` The Logic field also supports Excel formulas, like the following: - `EXACT(propertyId,'value')` - `ISNUMBER(propertyId) ` - `SUM(propertyId, propertyId)` > [!TIP] > If you want your workflow to always follow a given path, you can enter `TRUE` in the link's Logic field. Because you've hardcoded the value, the logic always evaluates as true. > [!NOTE] > Expressions that begin with an equal sign (=) are also valid. For example, =`EXACT(propertyId,'value')` and `EXACT(propertyId,'value') evaluate the same way`. The Property ID should reference a field accessible to your workflow. For example, a field present in the workflow submission. The Logic field autopopulates Property ID values as you enter text. > [!TIP] > You can use dot notation to reference keys under a given Property ID. For example, referencing a key/value pair in an object. > [!NOTE] > When entering a Property ID in your logic expression, you do not need to include `data.` as a prefix. Logic expressions support the following operators: `=, <, >, >=, <=`. When entering the criteria (value) the formula matches against, you can use a string, integer, or Boolean value. You must wrap strings in single (`'`) or double (`"`) quotes. Numerical values do not need quotes. To reference Boolean values, use `TRUE` or `FALSE`. |
| **Default** | This setting makes this link the Default link. If no other links evaluate as true, the workflow follows the Default link. You can only have a single Default link per Conditional Event node. When the Default setting is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_ON(9).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) **(ON)**, you cannot enter a logic expression for the link. The Default setting is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF(4).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) **(OFF)** by default. |
| **Unidirectional** | Sets the link one-way. End-users cannot navigate back through a unidirectional link. The link has a double arrowhead when the Unidirectional setting is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_ON(9).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) **(ON)**. The link has a single arrowhead when the Unidirectional setting is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF(4).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) **(OFF)**. By default, the Unidirectional setting is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF(4).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) **(OFF)**. |
| **Use Flash Message** | When set to ON, you can create a flash message for this link. Flash Messages are alerts that display at the top of the workflow in Express View. They show when an end-user navigates past a link that has a Flash Message enabled. By default, the Use Flash Message setting is ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF(4).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) **(OFF)**. |

## Adding a Conditional Event Node

For this example, set up a workflow that verifies an insurance applicant’s eligibility to receive a discount. Use a Conditional Event node to determine if the applicant meets the minimum requirements to qualify for the discount.

If the Conditional Event node's logic statement evaluates as **true**, the workflow follows the link to an external node. If the logic is **false**, the workflow proceeds to the next Sub-Process task. If there are no further Sub-Process tasks, the Sub-Process is complete, and the flow ends.

> [!NOTE]
> Conditional Event logic evaluation only happens on Sub-Process forward navigation.

This configuration assumes you've created a workflow and have access to modules in the training environment.

### Configure the Sub-Process and Task Nodes

First, add the [Sub-Process](/v1/docs/sub-process-node) node and accompanying [Task](/v1/docs/task-node) nodes to the Authenticated swimlane. You can connect the Task nodes to your own modules, or use the Enablement Lab modules in the following instructions.

1. In the Workflow Builder, drag and drop a **Sub-Process** node into the **Authenticated** swimlane.
2. Drag and drop three **Task** nodes inside the **Sub-Process** node.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional_Event_Node_SubProcess_Example.webm?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)
3. Select a **Task** node and click **Edit**.
4. In the **Label** field, enter `Step 1`.
5. From the **Module** drop-down, enter or select `Enablement Lab: Step 1 - Registration Info Conditional Event`.
6. Click **X** (Close).
7. Repeat this process for the other **Task** nodes using the following information:

| **Label** | Module |
| --- | --- |
| **Step 2** | Enablement Lab: Step 2 - Insurance Type Conditional Event |
| **Discount Eligibility** | Enablement Lab: Confirmation - Conditional Event |
8. Click **X** (Close).
9. Connect the output port (right) of the **Start** node to the input port (left) of the **Sub-Process** node.

### Configure the First End Node

This first [End](/v1/docs/end-node) node marks the end of your workflow if the Conditional Event logic is false.

1. Drag and drop an **End** node into the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `End 1`.
4. Click **X** (Close).
5. Connect the output port (right) of the **Sub-Process** node to the input port (left) of the **End** node.

### Configure the Conditional Event Node

Now you're ready to set up the Conditional Event and associated logic.

1. Drag and drop a **Conditional Event** node onto the Sub-Process node. [An animated image showing a workflow. The conditional event node is added to a sub-process node.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional_Event_Node_AddConEvent_Example.webm?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)
2. Click **Edit**.
3. In the **Label** field, enter `History of Claims`.
4. Click **X** (Close).

### Configure the Fourth Task Node

Next, set up the fourth [Task](/v1/docs/task-node) node. Your workflow proceeds to this node if the Conditional Event logic is true. If your applicant has not made any claims in the past three years, they see the discount approval message in the linked module.

1. Drag and drop a **Task** node into the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `Discount Approved`.
4. From the **Module** drop-down, enter or select `Enablement Lab: Confirmation - Conditional Event - Discount`.
5. Click **X** (Close).

### Configure the Conditional Event Link

Next, configure the Conditional Event Link to set up the logic that determines whether to display the discount approval message.

The `claimsHistory` Property ID represents a [Radio Buttons](/v1/docs/radio-buttons-component) component question in the `Step 2` module. The question asks your applicant if they have made any claims in the past three years. The `claimsNo` value is stored in the submission data when your applicant answers `No`.

If your applicant answers `No` in the `Step 2` module, they proceed to the `Discount Approved` **Task** node. There, they see a discount approval message. If they answer `Yes`, they proceed to the `Discount Eligibility` **Task** node in the Sub-Process node. There, they see a message that explains their ineligibility.

1. Connect the output port (bottom) of the `History of Claims` **Conditional Event** node to the input port (left) of the `Discount Approved` **Task** node. This connector becomes a Conditional Event Link.
2. Select the **Conditional Event Link** and click **Edit**.
3. In the **Label** field, enter `No Claims`.
4. In the **Logic** field, enter `claimsHistory="claimsNo"`. The Conditional Event link icon changes from ![unlinked](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Unlinked_Workflow.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) (unlinked) to ![linked](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Linked_Workflow.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D) (linked).
5. Click **X** (Close).

### Configure the Second End Node

Lastly, add a second [End](/v1/docs/end-node) node to finish the workflow after your applicant views the approval message.

1. Drag and drop a second **End** node into the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `End 2`.
4. Connect the output port (right) of the `Discount Approved` **Task** node to the input port (left) of the `End 2` **End** node.
5. Click **X** (Close).
6. Click **Save...**.
7. Click **Save**.

Your completed workflow looks like the following:

[![A static image displaying a completed workflow using a Conditional Event node.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional_Event_Node_Example_Complete_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Conditional%20Event%20Node%20Example%20Complete.jpg?sv=2026-02-06&spr=https&st=2026-11-15T00%3A56%3A15Z&se=2026-11-15T01%3A56%3A15Z&sr=c&sp=r&sig=LR31mLua8mJx4aomsqqHA6CBwofJqPUA7VDWDxaWx6A%3D)

A query lets you retrieve, access, manipulate, and delete data in a database.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

Also known as Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections.