---
title: "Timer Start Node"
slug: "timer-start-node"
tags: ["workflow-builder", "workflow-builder-nodes"]
status: "update"
updated: 2026-10-13T15:37:41Z
published: 2026-10-13T15:37:41Z
canonical: "docs.unqork.io/timer-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.

# Timer Start Node

The Timer Start node begins a workflow automatically on a timer schedule. Unlike the Timer node, which pauses an in-progress workflow, the Timer Start node initiates a new workflow instance at the scheduled time.

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]
> If the timer is currently active, settings are read-only. Stop the timer before making changes. For manual starts, see [Start Node](/unqorkai/docs/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 | `timerStart-{n}` | A display name for the node. |
| Path | `nodeId` | Text input | — | The unique identifier automatically generated for the node. Preset and not editable. |
| Type | `timerType` | Radio button | **Relative** | The scheduling mode to use. Options include: **Relative**, **Exact**, or **Cron**. |

> **Relative** (default): Begins the workflow after a set amount of time.
> 
> 
> | Setting | Field | Type | Default | Description |
> | --- | --- | --- | --- | --- |
> | Time Amount | `timeAmount` | Number input | — | The duration to wait before beginning. |
> | Time Unit | `timeUnit` | Drop-down | — | The unit of time. Options include: **Minutes**, **Hours**, **Days**, **Weeks**, **Months**, or **Years**. |

> Begins the workflow at a specific scheduled time.
> 
> 
> | Setting | Field | Type | Default | Description |
> | --- | --- | --- | --- | --- |
> | Frequency | `frequency` | Drop-down | — | How often to fire. Options include: **Daily**, **Weekly**, **Monthly**, or **Yearly**. |
> | ↳ Day of Week | `dayOfWeek` | Drop-down | — | The day to fire. Options include: **Monday**, **Tuesday**, **Wednesday**, **Thursday**, **Friday**, **Saturday**, or **Sunday**. Visible when **Frequency** is **Weekly**. |
> | ↳ Day of Month | `dayOfMonth` | Drop-down | — | The day of the month to fire. If the selected day doesn't exist in a given month, the timer fires on the last day of that month. Visible when **Frequency** is **Monthly** or **Yearly**. |
> | ↳ Month | `monthOfYear` | Drop-down | — | The month to fire. Options include: **January** through **December**. Visible when **Frequency** is **Yearly**. |
> | Time | `time` | Time input | — | The time of day to fire, in UTC. |

> Begins the workflow based on a cron expression for advanced scheduling.
> 
> 
> | Setting | Field | Type | Default | Description |
> | --- | --- | --- | --- | --- |
> | Cron Expression | `cronExpression` | Text input | — | A valid cron expression defining the schedule (for example, `0 9 * * 1` runs every Monday at 9:00 AM). |

## Link Settings

All links connecting to and from this node use the standard link settings panel. For the full reference, see [Output Links](/unqorkai/docs/output-links).

- **Label**: A display name for the link.
- **Status**: A descriptive label for the  this link represents. Use it to identify which route the workflow took, for example, `Approved` or `Rejected`.
- **Unidirectional**: When set to **ON**, this setting lets the workflow proceed without waiting for this path to complete.
- **Use Flash Message**: When set to **ON**, this setting displays a notification to end-users when the workflow follows this link.
  - **Flash Message**: The notification message to display.
  - **Make Flash Message Dismissable**: When checked, this setting lets end-users dismiss the notification.
  - **Message Status**: The visual style of the notification. Options include: **Success**, **Info**, or **Danger**.

---

**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.

The Number data type accepts integer or floating point values. The number data type does not use quotes around numerical values.

To execute or perform a a task. In the Operations builder, Events fire (execute) one, or multiple Operations.

Coordinated Universal Time (UTC) is a standard, globally-accepted timezone used to regulate clocks and time around the world.

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.