---
title: "Timed Event Node"
slug: "timed-event-node"
description: "Learn how the Timed Event node enhances workflows by triggering actions when tasks exceed time limits, ensuring timely task completion and accountability."
updated: 2025-12-04T21:43:42Z
published: 2025-12-09T16:46:27Z
canonical: "docs.unqork.io/timed-event-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.

# Timed Event Node

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timedEventNodeAnimation.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)The **Timed Event node** triggers specific actions when a task or sub-process doesn't complete in a specified time. Once the [workflow](/v1/docs/introduction-to-workflow) reaches a [Task](/v1/docs/task-node) or [Sub-Process](/v1/docs/sub-process-node) node, the Timed Event node begins tracking the time spent on that task.

Examples of when you would use the Timed Event node include:

- A Customer Support Specialist (CSS) needs to complete a response to a ticket within four hours after it enters their queue. After two hours, they receive an email reminding them to complete their work in two hours. After three hours, the customer support specialist and their manager receive an email. When the four hours expire, the workflow reassigns the task for the manager to complete.
- A user begins signing up for coverage but leaves the site before completing it. After three days, they receive an email from marketing to complete the form.

It's important to note that:

- You cannot add a Timed Event node to an Automated swimlane. But it can trigger a node that exists in the Automated swimlane.
- You can add Timed Event nodes onto a Sub-Process node. The countdown timer starts if the optional condition is true and when the workflow navigates to any node in the Sub-Process node.

## 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 task editing options and a timed event indicator.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timedEventNode.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)

| **Setting** | Description |
| --- | --- |
| **Edit** | Takes you to the Edit Timed Event drawer, where you can configure related settings. |
| **Delete** | Removes the node from the workflow. |

### Edit Timed Event Drawer Description

The following settings are available in the **Edit Timed Event** drawer:

![Editing a timed event with options for actions and workflow triggers.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timedEventNodeDrawer.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)

| **Setting** | Description |
| --- | --- |
| **Label** | The name of the node. By default, the Label displays as `timedEvent-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. |
| **Activate When...** | By default, a Timed Event node activates when the workflow reaches its associated step. You may also define a Boolean validation of the [submission data](/v1/docs/submission-data) to trigger the Timed Event node. For example, if `user_state=”New York”` is entered in this field, the Timed Event begins only when the workflow enters the step and `user_state=”New York”.` |
| **Actions** | A Timed Event node can take two different types of actions. These include sending an email message and sending the workflow to a new task. |
| **Send a Message** | You can define an unlimited number of email messages that can be sent if the workflow doesn’t complete the task or sub-process after a specified amount of time. Each message can have a delivery method, receiver, subject, content, and duration. > [!TIP] > This process works in the same way as the [Message](/v1/docs/message-node) node. |
| **Send Workflow to New Task After Certain Duration** | By linking a task or sub-process to the Timed Event node, your workflow moves on to that task after a specified time if the associated task or sub-process isn't completed. Once you link a task to the Timed Event Node, you can edit the link to define a label and time before the workflow moves on to that specified task. While you can define unlimited email messages sent using a Timed Event node, you can only assign a single workflow change. That way, the Timed Event is no longer valid once the workflow moves the new task. |
| **Close (****X****)** | Closes the Edit Timed Event drawer, returning your focus to the pool. |

### Add a Message Modal

Clicking on the Add a Message button displays the Add a Message modal. These settings are similar to the Message Node in function, and sending messages requires a service integration like Twilio.

![Form fields for adding a timed message with delivery method and template options.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timedEventAddMessage.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)

| Setting | Description |
| --- | --- |
| Message Label | Enter a Subject header for this message. |
| Send Message Via | Select a service for sending this message. Additional fields might display depending on the type of service selected. For example, selecting the **Email** service displays the **Subject** field. > [!NOTE] > Learn more about services in our [Services Administration](/v1/docs/services-administration) article. |
| To | Enter a value. Depending on the service, this value might be an email address, a phone number, or Creators can use a dynamic value from their application. For example, `{{ client.PhoneNumber }}`. |
| Send Message After This Duration | Specify the days, hours, and minutes before the message is sent. By default, messages are sent immediately after the node triggers. |
| Message Template | Enter a message. Messages support dynamic values, for example, `{{ client.firstName }}`. |

## Demonstration of a Timed Event Node

In this example, set up a workflow for a CSS support ticket intake process.

It consists of three [swimlanes](/v1/docs/swimlane-management):

- **Authenticated**: Where the end-user can submit a support ticket.
- **Administrator**: Where the CSS gets assigned the ticket to complete the ticket.
- **Automated**: Where the workflow assigns the ticket to the CSS. And where the workflow validates if the ticket was completed on time.

Because critical (P1 - High) tickets should be resolved on time, a Timed Event node will send various email messages based on the following configuration:

1. The CSS receives a reminder email if the critical ticket isn't resolved in two hours.
2. If the critical ticket isn't resolved in three hours, the CSS receives another reminder email, and their manager receives an email that the ticket isn't resolved.
3. If the critical ticket isn't resolved in four hours, it is reassigned to the manager.

If the CSS tries to complete the ticket after four hours, they receive an error message. This error message confirms that the task is no longer available because it has been reassigned to the manager.

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

### Configure the Authenticated Task Node

First, add a Task node to the Authenticated swimlane. This first Task node lets your end-user submit a support ticket.

1. Drag and drop a **Task** node into the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `Ticket Details`.
4. From the **Module** drop-down, enter or select `SLA Reporting: Ticket Details`.
5. Click **X** (Close).
6. Connect the output port (right) of the **Start** node to the input port (left) of the `Ticket Details` **Task** node.

> [!NOTE]
> You'll connect the remaining **Task** node at a later time.

### Configure the Administrator Task Nodes

Add two Task nodes to the Administrator swimlane. Both Task nodes use the same SLA Reporting: Ticket Summary module. The first Task node lets the CSS select the ticket (In Progress). You'll associate the Timed Event node with this Task node later. The second Task node provides a ticket summary after completing the ticket (Complete).

1. Drag and drop two **Task** nodes into the **Administrator** swimlane.
2. Click **Edit** and configure each **Task** node as follows:

| # | **Label** | Path | **Module** |
| --- | --- | --- | --- |
| 1 | **Ticket - In Progress** | ticketinprogress | SLA Reporting: Ticket Summary |
| 2 | **Ticket - Complete** | ticketcomplete | SLA Reporting: Ticket Summary |
3. After editing each **Task** node, click **X** (Close).

> [!NOTE]
> You'll connect these **Task** nodes at a later time.

### Configure the Automated Task Nodes

Next, add three Task nodes to the Automated swimlane. The first Task node contains an API module that assigns the submitted ticket to the CSS. If the CSS completes the ticket in four hours, they navigate to the second Task node, which confirms the ticket is complete. If the CSS doesn't complete the ticket in four hours, they navigate to the third Task node. At this point, they can't complete the task because it is reassigned to the manager. You'll connect the Timed Event node to this third Task node later.

1. Drag and drop a **Task** node into the **Automated** swimlane.
2. Click **Edit** and configure each **Task** node as follows:

> [!NOTE]
> Automated Tasks display a different drawer when compared to User Tasks. For this example, the **Select Task Type** is set to **Script**.

| **Label** | Path | **Module** |
| --- | --- | --- |
| **Assignment** | assignment | SLA Reporting: Assignment |
| **Met SLA** | metsla | SLA Reporting: Met SLA |
| **Missed SLA** | missedsla | SLA Reporting: Missed SLA |
3. After editing each **Task** node, click **X** (Close).
4. Connect the output port (right) of the `Ticket Details` **Task** node to the input port (left) of the `Assignment` **Task** node.
5. Connect the output port (right) of the `Assignment` **Task** node to the input port (left) of the `Ticket- In Progress` **Task** node.
6. Connect the output port (right) of the `Ticket - In Progress` **Task** node to the input port (left) of the `Met SLA` **Task** node.
7. Connect the output port (right) of the `Met SLA` **Task** node to the input port (left) of the `Ticket - Complete` **Task** node.

### Configure the Timed Event Node

Add a Timed Event node onto the `Ticket - In Progress` **Task** node to configure the four-hour completion window. This configuration only applies to critical tickets submitted by your end-user. You'll then connect its output to the `Missed SLA` **Task** node to reassign the ticket if it's not completed in four hours. You'll also set up three emails to be sent by the Timed Event node at specific times.

> [!NOTE]
> For the email messages, use your email address for each to test the Timed Event.

1. Drag and drop a **Timed Event** node onto the `Ticket - In Progress` **Task** node. [Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/TimedEvent_Add.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)
2. Click **Edit**.
3. In the **Label** field, enter `Timed Event - Critical`.
4. Click **Add a Message**. The Add a Message modal displays.
5. In the **Message Label**, enter `Reminder: Complete Support Ticket`.
6. From the **Send Message Via** drop-down, select **Email**.
7. In the **Subject** field, enter `Reminder: Complete Support Ticket`.
8. In the **To** field, enter your email address. This email address represents the email address of the CSS.
9. In the **Send Message After This Duration** section, set the **Hours** field to `2`.
10. In the **Message Template** field, enter `Please complete the support ticket in two hours.`.
11. Click **Save**.
12. Repeat steps four through ten two more times using the following information:

| # | **Message Label** | Send Message Via | Subject | To | Send Message After This Duration | Message Template |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | **Reminder: Complete Support Ticket** | **Email** | Reminder: Complete Support Ticket | Your email address (CSS) | 3 hours | Please complete the support ticket in one hour. |
| 2 | **Notice: Incomplete Support Ticket** | **Email** | Notice: Incomplete Support Ticket | Your email address (Manager) | 4 hours | Your CSS has yet to complete the support ticket. They have one hour to complete the ticket. |
13. Click **Save** after completing each message.

### Configure the Timed Event Link

Set up the Timed Event link between the `Timed Event - Critical` **Timed Event** node and the `Missed SLA` **Task** node.

1. Connect the output port (bottom) of the `Timed Event - Critical` **Timed Event** node to the input port (left) of the `Missed SLA` **Task** node.
2. Click **Edit**.
3. In the **Label** field, enter `4 Hours`.
4. In the **Duration of Timer** section, set the **Hours** field to `4`.

> [!NOTE]
> The duration must be greater than or equal to the durations set for the node's messages. Once the workflow moves onto a new task, the Timed Event is no longer valid and cannot send messages.
5. Click **X** (Close).

### Configure the End Node

Finally, configure an End node to finish the workflow after the CSS completes the ticket.

1. Drag and drop an **End** node into the **Administrator** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `End`.
4. Connect the output port (right) of the `Ticket - Complete` **Task** node to the input port (left) of the `End` **End** node.
5. Click **X** (Close).
6. Click **Save...**.
7. Click **Save**.

Your completed workflow looks like the following:

[![Flowchart illustrating ticket reporting process from start to completion stages.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/timedEventWorkflow.webp?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/TimedEvent%20FinalWF.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)

## Testing Your Timed Event

Test the Timed Event in Express View. Preview your workflow.

In the top-right of the page:

1. Click **Show**.
2. From the **Preview As** drop-down, select **Authenticated**.
3. In the **Summary*** and **Description*** fields, enter some test information.
4. From the **Team*** drop-down, select an option.
5. From the **Severity*** drop-down, select **P1 - High**. Remember, the Timed Event only works for the P1 - High priority tickets.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/TimedEvent_Auth.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)
6. Click **Next**.

After the new page loads, from the **Preview As** drop-down, select **Administrator**. Do not click **Next**. In two hours, you'll receive the first email. In three hours, you'll receive the other two emails. After four hours, click **Next**. An error message displays because the task is no longer available and has been reassigned to the manager.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/TimedEvent_Admin.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A39Z&se=2026-11-07T18%3A57%3A39Z&sr=c&sp=r&sig=amWTUaF9oT5Kff9g2hHsHOHIUoic0rkuc9J23aj4BIk%3D)

> [!TIP]
> For a faster test, change the message and node durations to one minute.

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.

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.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

A modal is a window that appears on top of the content you are currently viewing.

Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.