---
title: "Handoff Node"
slug: "handoff-node"
updated: 2025-12-08T20:09:20Z
published: 2025-12-09T16:46:27Z
canonical: "docs.unqork.io/handoff-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.

# Handoff Node

![A static image of a Handoff Node](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Handoff%20Node.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

The **Handoff node** acts as an ending point for a [workflow](/v1/docs/introduction-to-workflow). Once a workflow reaches the Handoff node, it transfers to another workflow. The Handoff node also controls submission data transferred to the next workflow.

You'll find the Handoff node in the list of nodes to the left of the [Workflow Builder](/v1/docs/introduction-to-workflow).

### Similar Nodes

The Handoff node has similar functionality to the End node. However, they each serve a different purpose:

- **Handoff node**: Connects the end of a workflow to another workflow. Handoff nodes can transfer the current submission data to the new workflow, or end it at the Handoff node.
- [**End node**](/v1/docs/end-node): Ends a workflow, or redirects to a module or URL.

## 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:

![Interface showing an editable option for the 'handoff-1' element in a design tool.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Handoff%20Node%20-Edit.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

| **Setting** | Description |
| --- | --- |
| **Edit** | Takes you to the Edit Handoff Event window, where you can configure related settings. |
| **Open** | This setting is enabled after you've set a hand-off location for the node. After setting this location, you'll click **Open** to access your connected workflow. That way, your existing workflow stays open, and your handoff workflow displays in a new tab. |
| **Delete** | Removes the node from the workflow. |

### Edit Handoff Event Window Description

Clicking the **Edit** button displays the **Edit Handoff Event** window with the following settings:

| **Setting** | Description |
| --- | --- |
| **Label** | Sets the name of your node. By default, the Label displays as handoff-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. |
| **Continue Current Submission** | When the toggle is ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(ON)**, the current submission ID is used. When this toggle is ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(OFF)**, a new submission ID is generated after a workflow hands off to another workflow. By default, Continue Current Submission is set to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(ON)**. |
| **Choose Workflow To Hand Off To** | Defines which workflow your current workflow connects to after the handoff. |
| **X (Close)** | Closes the **Edit Handoff Event** window, returning your focus to the pool. |

## Adding a Handoff Node

For this use case, create two [workflows](/v1/docs/workflow-links). The first navigates end-users through an `Account Selection` **workflow**. The second workflow navigates end-users through an `Account Information` **workflow**. You’ll use a Handoff node to transfer end-users from one workflow to the other.

This example assumes that you've set up your modules in advance and have new workflows ready.

### Configure the First Workflow

In this workflow, a [Task](/v1/docs/task-node) node calls an `Account Information` module, where end-user submit their data. Then the Handoff node passes the end-user from the current workflow to the next one.

#### Configure the Start Node

1. Select the **Start** node.
2. Click **Edit****.**
3. In the **Label** field, enter **First Start Node**.
4. Click `X` (Close).

#### Configure the Task Node

1. Drag and drop a **Task** node into the **Authenticated** swimlane.
2. Click **Edit.**
3. In the **Label** field, enter `Account Information`.
4. From the **Module** drop-down, enter or select `Enablement Lab: Account Information`. This module stores the general account information related to individual accounts.

[![User task editing interface showing account information and module details.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Account%20Information%20Edit%20screen.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Handoff%20Node%20wf1%20usertask.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)
5. Click **X** (Close).
6. Connect the output port (right) of the **Start** node to the input port (left) of the **Task** node.

#### Configure the Handoff Node

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

> [!NOTE]
> You'll connect the Handoff node to the next workflow at a later stage.

Your first workflow looks like the following:[![Flowchart showing account information process with start node and handoff to account selection.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Acct%20Info%20Workflow.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Handoff%20Node%20wf1%20complete.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

### Configure the Second Workflow

The second workflow begins with the end-user submitting their account choice in the `Account Selection` module. Then, they're directed to one of two paths. They'll either complete their application for a 401K account or for an IRA account.

#### Configure the Start Node

1. Select your **Start** node.
2. Click **Edit**.
3. In the **Label** field, enter `Main Start Node`.
4. Click **X** (Close).

#### Configure the Task Nodes

Add three [Task](/v1/docs/task-node) nodes to your workflow. The first Task node connects to the `Account Selection` module. The other two Task nodes capture information about the different account types.

1. Drag and drop three **Task** nodes into the **Authenticated** swimlane.
2. Select the first **Task** node and click **Edit****.**
3. In the **Label** field, enter `Account Selection`. The **Path field** updates with a new path based on the `Label field` value.
4. From the **Module** drop-down, enter or select `Enablement Lab: Account Selection Module`.
5. Click **X** (Close).
6. Repeat this process for the other **Task** nodes using the following information:

| # | **Label** | Module |
| --- | --- | --- |
| 1 | 401K | Enablement Lab: 401K Account Module |
| 2 | IRA | Enablement Lab: IRA Account Module |
7. Connect the output port (right) of the **Start** node to the input port (left) of the `Account Selection` **Task** node.

> You'll connect the remaining Task nodes at a later stage.

#### Configure the Exclusive Gateway Node

An [Exclusive Gateway](/v1/docs/exclusive-gateway-node) node uses logic to split your end-user's journey into two or more paths. You can think of an Exclusive Gateway node as a workflow's version of the [Decisions](/v1/docs/how-to-guide-decisions-component) component. Much like you can use the Decisions component to set if/then rules, you can use Gateway nodes to set if/then journeys.

1. Drag and drop a **Exclusive Gateway** node into the **Authenticated** swimlane.
2. Connect the output port (right) of the `Account Selection` **Task** node to the input port (left) of the **Exclusive Gateway** node.

#### Configure the Exclusive Gateway Links

1. Connect the output port (right) of the **Exclusive Gateway** node to the input port (left) of the `401K` **Task** node.
2. Click **Edit**.
3. In the **Label** field, enter `rule401K`.
4. In the **Logic** field, enter `accountRegistrationType="401K"`. When selecting `401K` in the **Account Selection** module, this logic sends your end-user to the 401K Registration process.

[![Flowchart illustrating account selection and gateway logic for 401K and IRA modules.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Exclusive%20Gateway%20Edit.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Handoff%20Node%20wf2%20401link.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)
5. Click **X** (Close).
6. Connect the output port (right) of the **Exclusive Gateway** node to the input port (left) of the `IRA` **Tas**k node.
7. Click **Edit**.
8. In the **Label** field, enter `ruleIRA`.
9. In the **Logic** field, enter `accountRegistrationType="IRA"`. By selecting `IRA` in the **Account Selection** module, this logic sends your end-user to the IRA Registration process.
10. Click **X** (Close).

#### Configure the End Nodes

Add two [End](/v1/docs/end-node) nodes as termination points for your workflow.

1. Drag and drop two **End** nodes into the **Authenticated** swimlane.
2. Connect the output port (right) of the `401K` **Task** node to the input port (left) of the `end-1` **End** node.
3. Connect the output port (right) of the `IRA` **Task** node to the input port (left) of the `end-2` **End** node.
4. Click **Save…**.
5. Click **Save**.

Your second workflow looks like the following when completed:

[![Flowchart illustrating account selection process with 401K and IRA modules.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Account%20Selection%20Workflow.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Handoff%20Node%20wf2%20complete.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

### Configure the First Workflow's Handoff Node

Return to your first workflow and connect it to the second workflow using the Handoff node.

1. Return to the first Workflow and select the **Handoff** node.
2. Click **Edit**.
3. From the **Choose Workflow to Hand Off To** drop-down, enter or `select the name of your second workflow`.
4. From the **Choose Node to Start From** drop-down, select **Main Start Node**.
5. Click **X** (Close).
6. Click **Save…**.
7. Click **Save**.

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.

A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.

Focus indicates the element of the graphical user interface which is currently selected to receive input. Elements with focus sometimes have an accesibility border highlighted around them.

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.

A definition

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.

In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module.

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.