---
title: "Start Node"
slug: "start-node"
tags: ["workflow-builder", "workflow-builder-nodes"]
status: "update"
updated: 2026-10-13T15:37:20Z
published: 2026-10-13T15:37:20Z
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

The Start node is one way to begin a workflow. It serves as the default entry point and is triggered manually or programmatically. Every workflow requires at least one Start node—use **Set as Default Start** when the workflow has multiple Start nodes to define which one runs by default.

Unqork provides three ways to begin a workflow:

- **Start node**: the default entry point. Triggered manually by an end-user or programmatically by another workflow or component.
- **Timer Start node**: triggers automatically on a schedule. Supports relative, exact, and cron-based timing.
- **Signal Start node**: triggers when a specific signal event is received from another workflow or an external source.

> [!NOTE]
> For time-based starts, see [Timer Start Node](/unqorkai/docs/timer-start-node). For event-based starts, see [Signal Start Node](/unqorkai/docs/signal-start-node).

> **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 | — | A display name for the node. |
| Path | `nodeId` | Text input | — | The unique identifier automatically generated for the node. Preset and not editable. |
| Set as Default Start | `default` | Toggle | OFF | When set to **ON**, this setting marks this node as the default entry point when multiple Start nodes exist. |

---

**Changelog**

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

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.

**Cron** is a time-based job scheduler in Unix-like operating systems that allows users to schedule commands or scripts to run automatically at specific times or intervals. These scheduled tasks, called "cron jobs," can be used for routine system maintenance like backups, software updates, or running custom scripts to perform tasks like deleting old files or sending out email notifications.

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