--- title: "Start Node" slug: "start-node" updated: 2026-01-30T17:21:31Z published: 2026-01-30T17:21:31Z canonical: "docs.unqork.io/start-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. # Start Node ![A static image displaying the Start Node button indicating initiation of a workflow.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/StartNode.jpg?sv=2026-02-06&spr=https&st=2026-10-26T11%3A28%3A19Z&se=2026-10-26T12%3A28%3A19Z&sr=c&sp=r&sig=xGiOB%2FgqDmeVqQtryjWzYhTIvRVWJ5aQaFy%2Bq0auoAk%3D) The **Start** **node** signifies the beginning of your [workflow](https://docs.unqork.io/docs/workflow-builder-menu-settings). It gets activated by events, like end-users accessing the page or a transition from another workflow. By default, new workflows include a Start node in the Authenticated [swimlane](https://docs.unqork.io/docs/swimlane-management). While workflows may include multiple Start, [Signal Start](/v1/docs/signal-start-node), or [Timer Start](/v1/docs/timer-start-node) nodes, at least one of these three is necessary for the proper functionality of the workflows. You'll find the Start node in the list of nodes on the left of the [Workflow Builder](/v1/docs/introduction-to-workflow). ### Similar Workflow Start Nodes While the names are similar, the Start node differs from the Signal Start node and Timer Start node. Here are the nodes compared: - **Start node**: Starts a workflow when triggered by an event. - [**Signal Start node**](https://docs.unqork.io/docs/signal-start-node): Starts a workflow when an event occurs, like module saves and application promotions. - [**Timer Start node**](https://docs.unqork.io/docs/timer-start-node): Automates the start of a workflow according to a schedule. ## 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: ![A static image displaying the options to edit or delete an item in a user interface menu.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/StartNodeSettings.jpg?sv=2026-02-06&spr=https&st=2026-10-26T11%3A28%3A19Z&se=2026-10-26T12%3A28%3A19Z&sr=c&sp=r&sig=xGiOB%2FgqDmeVqQtryjWzYhTIvRVWJ5aQaFy%2Bq0auoAk%3D) | **Setting** | Description | | --- | --- | | **Edit** | Takes you to the Edit Start window, where you can configure related settings. | | **Delete** | Removes the node from the workflow. | ### Edit Start Event Window Description Click the **Edit** button to display the **Edit User Task** settings window. ![A static image displaying the edit start event with label and path fields in a user interface.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/StartNode_EditSettings.jpg?sv=2026-02-06&spr=https&st=2026-10-26T11%3A28%3A19Z&se=2026-10-26T12%3A28%3A19Z&sr=c&sp=r&sig=xGiOB%2FgqDmeVqQtryjWzYhTIvRVWJ5aQaFy%2Bq0auoAk%3D) | **Setting** | Description | | --- | --- | | **Label** | Sets the name of the node. By default, the Label displays as `start-1`. The label is optional and displays below the node on the workflow canvas. Define labels by associating them with the role of the node. | | **Path** | The path of the node. By default, the Path displays as `start-1`. A path is a unique identifier that other components can reference. The Start node path is set automatically and isn't editable. | | **Set as Default Start** | You can have many Start nodes in a single workflow. But workflows can only have one Default Start node. Setting the Set as Default Start toggle to ON sets the node as the primary starting point in a workflow. In a new workflow with a single Start node, the Set as Default Start toggle is set to ON by default. For each additional Start node you add, the Set as Default Start toggle is set to OFF. To change the Default Start node, adjust the node's Set as Default Start toggles as needed. | | **Close** | Closes the Edit Start Event window, returning your focus to the pool. | ## Adding a Start Node This example outlines a workflow that includes a Start, [Task](/v1/docs/task-node), and [Handoff](/v1/docs/handoff-node) node. The Task node calls an **Account Information** module. Using this module, the end-user (an account applicant) can submit their data before handoff to the next step. > This demonstration is for illustrative purposes only and cannot be replicated in the [Training](https://training.unqork.io/) environment due to module RBAC limitations. > [!NOTE] > These instructions assume you have a new workflow open, saved, and with a title. ### 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 in the **Authenticated** swimlane. 2. Click **Edit**. 3. In the **Label** field, enter `Account Information`. 4. From the **Module** drop-down, create or select `Enablement Lab: Account Information`. ![A static image displaying the editing user task module with fields for label, path, and screen type options.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/StartNode_AccountInfo.jpg?sv=2026-02-06&spr=https&st=2026-10-26T11%3A28%3A19Z&se=2026-10-26T12%3A28%3A19Z&sr=c&sp=r&sig=xGiOB%2FgqDmeVqQtryjWzYhTIvRVWJ5aQaFy%2Bq0auoAk%3D) 5. Click **X** (Close). 6. Connect the output port (right) of the `First Start Node` **Start** node to the input port (left) of the `Account Information` **Task** node. ### Configure the Handoff Node Next, set up the [Handoff](/v1/docs/handoff-node) node that transitions the end-user to another workflow. In this example, use the Handoff node as a placeholder for practice purposes. 1. Drag and drop a **Handoff** node in the **Authenticated** swimlane. 2. Click **Edit**. 3. In the **Label** field, enter `Handoff to Main`. 4. From the **Workflow To Handoff To** drop-down, choose a workflow. > [!NOTE] > If you do not have a workflow for the handoff, skip this step. Note that an error occurs when trying to save or preview the workflow. 5. From the **Choose Node to Start From** drop-down, select a node. Doing os sets where the end-user begins in the next workflow. ![A static image displaying the interface for editing a handoff event with options for workflow and node selection.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/StartNode_HandOFF.png?sv=2026-02-06&spr=https&st=2026-10-26T11%3A28%3A19Z&se=2026-10-26T12%3A28%3A19Z&sr=c&sp=r&sig=xGiOB%2FgqDmeVqQtryjWzYhTIvRVWJ5aQaFy%2Bq0auoAk%3D) 6. Click **X** (Close). 7. Connect the output port (right) of the `Account Information` **Task** node to the input port (left) of the `Handoff to Main` **Handoff** node. 8. Click **Save...**. 9. Click **Save**. This is how the workflow looks when completed:![A static image displaying the workflow illustrating account information processing and handoff to main system.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/StartNodeConfiguration.jpg?sv=2026-02-06&spr=https&st=2026-10-26T11%3A28%3A19Z&se=2026-10-26T12%3A28%3A19Z&sr=c&sp=r&sig=xGiOB%2FgqDmeVqQtryjWzYhTIvRVWJ5aQaFy%2Bq0auoAk%3D) DOM (Document Object Model) events are signals or notifications that something has occurred or is occurring within a web page, often triggered by user interactions or by the browser itself. These events allow JavaScript to react to changes and interactions on a web page, making it dynamic and interactive. 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. DOM (Document Object Model) events are signals or notifications that something has occurred or is occurring within a web page, often triggered by user interactions or by the browser itself. These events allow JavaScript to react to changes and interactions on a web page, making it dynamic and interactive. In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module. 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. RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network.