---
title: "Timer Start Node"
slug: "timer-start-node"
description: "Automate tasks with the Timer Start node, triggering workflows on a schedule for data exports and email notifications. Optimize your system maintenance today!"
updated: 2025-12-08T19:39:16Z
published: 2025-12-09T16:46:27Z
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** enables automation by triggering the start of a [workflow](/v1/docs/introduction-to-workflow) on a preset schedule. For example, a Timer Start node can create integration and cron jobs, which are a time-based scheduler utility that automates system maintenance or administration.

You can use this node to achieve tasks like exporting data or sending emails at regular intervals. The Timer Start node can trigger at an exact time (Tuesdays at 15:30) or a relative time (every 11 hours) using UTC (Coordinated Universal Time).

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

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

![User interface showing timer controls with options to start, stop, and delete.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timerStart.webp?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 |
| --- | --- |
| **Edit** | Takes you to the Edit Timer Start Event drawer. Use the drop-down to access additional actions. |
| ↳ | **Start** | Activates the workflow, placing it into a running state. Once you start the node, the workflow repeats at the relative or exact time. The workflow runs on that interval until you click Stop. |
| **Stop** | Deactivates a running workflow and places it into a stopped state. |
| **Run Once** | Performs a test run of your workflow in a separate instance from the standard Run/Stop state of the workflow. You should always test your workflow to ensure it works correctly. The test runs until the workflow completes one cycle. |
| **Delete** | Removes the node from the workflow. |

## Starting and Stopping a Workflow's Run State

After adding a Timer Start node and completing your workflow, you can set its run state. In a run state, your workflow waits for the Timer Start node to begin. When it reaches the start time, the workflow runs from start to finish. Your workflow continues to run according to the defined schedule, repeating until stopped.

> [!WARNING]
> Stop any Timer Start nodes before removing the swimlane where they exist. You cannot remove a swimlane if it contains a running Timer Start node.

Start Run StateStop Run State

#### Starting Your Workflow's Run State

To start your workflow's run state:

1. Select your **Timer Start** node.
2. Click the **Edit** drop-down.
3. Select **Start**.

#### Stopping Your Workflow's Run State

To stop your workflow's run state:

1. Select your **Timer Start** node.
2. Click the **Edit** drop-down.
3. Select **Stop**.

> [!TIP]
> You can also use Start Node Administration to sort, start, and stop any Timer Start node in your environment. To learn more about this process, view our [Start Node Administration](/v1/docs/start-node-administration) article.

### Edit Timer Start Event Drawer

Clicking the **Edit** button displays the **Edit Timer Start Event** panel with the following settings:![Settings for a timer start event with label, path, and type options displayed.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timerStartDrawer.webp?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 the node. By default, the Label displays as `timerStart-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. |
| **Path** | The path of the node. By default, the Path displays as `timerStart-1`. A path is a unique identifier that other components can reference. |
| **Type** | The timer type you can select. |
| ↳ | **Relative** | Toggles the timer start time to **Relative**. A relative Timer Event repeats when an amount of time passes. For example, a relative Timer Event runs one time after a relative amount of time passes. > [!NOTE] > You can enter fractional units of time. For example, a relative time of 3.25 hours triggers every 195 minutes. |
| ↳ | **Time Amount** | Enter the amount of time. Time length is determined by the Time Unit setting. |
| **Time Unit** | Specify the Time Amount value’s unit type. Units include: - Minutes - Hours - Days - Weeks - Months - Years |
| **Exact** | Toggles the timer start time to **Exact**. An exact Timer Event repeats at a precise time of day on a frequency of daily, weekly, monthly, or yearly. For example, an exact time of a Weekly event at 15:50 starts every seven days at 15:50. |
| ↳ | **Frequency** | Specify how often the event should trigger. Frequency units include: - **Daily**: Triggers every day at the specified time (UTC). - **Weekly**: Triggers once a week on the specified day and time (UTC). - **Monthly**: Triggers once a month on the specified date and time (UTC). - **Yearly**: Triggers once a month on the specified month, date, and time (UTC). |
| **Cron** | Toggles the timer to use a **cron expression**. Cron expressions can run tasks periodically at fixed times, dates, or intervals. > [!TIP] > To learn more about using cron expressions, view our [Introduction to Cron Expressions](/v1/docs/introduction-to-cron-expressions) article. |
| **Close** | Closes the Edit Timer Event drawer, returning your focus to the pool. |

### Using Multiple Timer Start Nodes

Creators can use multiple Timer Start nodes to trigger a workflow at specific times. For example, the following workflow must trigger at the following times:

- Mondays at 08:00 UTC.
- Tuesdays at 10:00 UTC.
- Every 2 hours.

To achieve this process, configure each time in a separate Timer Start node. You can use multiple Timer Start nodes in a workflow, but it's a best practice to limit them to 20 Timer Start nodes per workflow. This limit ensures high performance and reduces server load.

## Demonstration of a Timer Start Node

For this example, you'll configure a simple workflow that includes a Timer Start, [Task](/v1/docs/task-node), and [End](/v1/docs/end-node) node. The workflow will run every Friday at 12 pm and generate an Excel report of submission data from an insurance application form. This example assumes you've set up your [module](/v1/docs/what-is-a-module) in advance and have created a [workflow-type](/v1/docs/working-with-workflow-type-apps) application.

> [!NOTE]
> This demonstration is for illustrative purposes only and cannot be replicated due to [Training](https://training.unqork.io/) environment security.

### Preconfiguration

When you create a new workflow, a Start node is automatically included. A workflow must have a Start or Timer Start node to function. For this example, delete the Start node.

1. Select the **Start** node.
2. Click the **Edit** drop-down.
3. Select **Delete**.

### Configure the Timer Start Node

1. Drag and drop a **Timer Start** node in the **Automated** swimlane.
2. Click the **Edit** button. The Edit Timer Start Event panel opens to the right.
3. In the **Label** field, enter `Timer Start`.
4. Set the **Type** to **Exact**.
5. From the **Frequency** drop-down, select **Weekly**.
6. From the **Day of Week** drop-down, select **Friday**.
7. In the **Time** field, enter `12:00 PM`. ![Settings for a timer start event, including frequency and time details.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timerStartNodeConfigure.webp?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)
8. Click **X** (Close).

### Configure the Task Node

You’ll link this node to a dashboard module to access the submission data.

1. Drag and drop a **Task** node in the **Automated** swimlane.

> [!NOTE]
> Task nodes added to the Automated swimlane operate as Script-type tasks.
2. Click the **Edit** button. The Edit Script Task panel opens to the right.
3. In the **Label** field, enter `Enablement Lab: Dashboard`.
4. From the **Module** drop-down, enter or select **Enablement Lab: Timer Start Dashboard**. This module displays an example dashboard that refreshes every time the workflow starts.
5. Click **X** (Close).

### Configure the End Node

1. Drag and drop an **End** node in the **Automated** swimlane.
2. Click the **Edit** button. The Edit End Event panel opens to the right.
3. In the **Label** field, enter `End`.
4. Click **X** (Close).
5. Click **Save...**.
6. Click **Save**.

## Promoting a Workflow With a Timer Start Node

Timer Start nodes are unique during a workflow promotion. Before promoting your workflow, you must stop all Timer Start nodes. After promotion, you must manually start them again. You can change the run status in the [Workflow Builder](/v1/docs/introduction-to-workflow) or by using [Start Node Administration](/v1/docs/start-node-administration).

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

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

A UI (User Interface) Drawer is a layout panel that slides out from the side of the screen to display content. In UDesigner, components display their configuration panels in a drawer.

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.