---
title: "Signal Start Node"
slug: "signal-start-node"
description: "Learn how to configure the Signal Start node in workflows to trigger actions from application promotions and saves, enhancing automation and efficiency."
updated: 2025-12-08T20:11:00Z
published: 2025-12-09T16:46:27Z
canonical: "docs.unqork.io/signal-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.

# Signal Start Node

![Icon representing signalStart-1 with a triangular shape for signaling purposes.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Signal_Start_Node.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)The **Signal Start node** is one of three nodes that begin a workflow. Like the [Start](/v1/docs/start-node) node, Workflows can have multiple Signal Start nodes. Unlike the Start node, the Signal Start node triggers from application promotions or save events. To use a Signal Start node, you must configure the settings, save your workflow, and select **Run** or **Test Run**.

The Signal Start node can be set to trigger from the following events:

- On specific or all application promotions.
- On specific or all module saves.
- On specific or all workflow saves.

The Signal Start node is located in the list of nodes to the left of the [Workflow Builder](/v1/docs/introduction-to-workflow).

### Similar Workflow Nodes

While the names are similar, the Start node differs from the Signal Start node and Timer Start node. Below are the differences:

- **Signal Start** **node**: Starts a workflow when an event occurs, like Module saves and application promotions.
- [**Start node**](/v1/docs/start-node): Starts a workflow when triggered by an event.
- [**Timer Start node**](/v1/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:

![Menu options including Edit, Start, Stop, Run Once, and Delete buttons displayed.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Signal_Start_Edit.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)

| **Setting** | Description |
| --- | --- |
| **Edit** | Takes you to the **Edit Signal Start Event** window, where you can configure settings relating to the Signal Start node. |
| **Delete** | Removes the node from the workflow. |
| **Run** | Activates the workflow and puts it in a running state. Once you start the node, it waits for events to run. It continues to run until you click **Stop**. |
| **Stop** | Deactivates a running workflow and puts it in a stopped state. A stopped state means the node no longer listens for a save event of the selected module or promotion of the selected application. |
| **Test Run** | Performs a test run of your workflow. This Test Run is separate from the normal Run/Stop state. The test runs until the workflow completes one cycle. You should always test your workflow to ensure it behaves as expected. |

### Edit Signal Start Event Window Description

Click the **Edit** button to display the **Edit Signal Start Event** window. The following settings are available in the **Edit Signal Start Event** window:

![Editing the signal start event with label and path fields displayed.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Signal_Start_Drawer.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)

| **Setting** | Description |
| --- | --- |
| **Label** | The name of the node. By default, the Label displays as `signalStart-1`. This label is optional and displays on the node once set. |
| **Path** | The Path of the node. By default, the Path displays as `signalStart-1`. The Path is a unique identifier that other components can reference. |
| **Triggering Event** | There are six triggering events to choose from: - **On Promotion (Specific Application)**: Triggers your workflow once you promote your application to the next environment. - **On Promotion (All Applications)**: Triggers your workflow once you promote any application to the next environment. - **On Save (Specific** **Module****s)**: Lists all the modules in your environment. When you save the selected module, your workflow triggers. - **On Save (All** **Module****s)**: Lists all the modules in your environment. Saving any module in your workspace triggers your workflow. - **On Save (Specific Workflow)**: Lists all the workflows in your environment. When you save the selected workflow, your workflow triggers. - **On Save (All Workflows)**: Lists all the workflows in your environment. Saving any workflow in your workspace triggers your workflow. |

## Adding a Signal Start Node

In this example, set up a simple workflow that includes a Signal Start node. This example assumes that you've set up your module in advance and that you have a workflow set up.

### Remove the Default Start Node

1. On the Workflow Builder canvas, select the **Start** node.
2. Click **Delete**.

### Configuring the Signal Start Node

1. Drag and drop a **Signal Start** node in the **Authenticated** Swimlane.
2. Click **Edit****.**
3. In the **Label** field, enter `Confirmation Email Start`.
4. From the **Triggering Event** drop-down, select **On Save** **(Specific** **Module****)**.
5. From the **Module** drop-down, select **Enablement Lab: Message Use Case - General Info**.

> [!NOTE]
> This module triggers your Signal Start node.

[![Editing a signal start event with label and triggering event details displayed.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Signal_Start_Settings.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/SignalStart%20node%20config1.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)
6. Click **X** (Close).

### Configuring the Message Node

Use a [Message](/v1/docs/message-node) node to send a confirmation email to your end-user acknowledging receipt of their basic information.

1. Drag and drop a **Message** node in the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `Confirmation Email`.
4. From the **Send via** drop-down, select **Email**.
5. In the **To** field, enter `{{data.email}}`.

> [!NOTE]
> The `{{data.email}}` syntax references the value your end-user enters in the **Email** field of the **General Information** module.
6. In the **From Name** field, enter `Unqork` or a custom sender name.
7. In the **Reply To** field, enter `no-reply@unqork.com` or a custom sender address.
8. In the **Subject** field, enter `Thank you for applying`.
9. In the **Template** field, enter the following:

`Hi {{data.firstName}},`

`Thank you for submitting your application. We'll be in touch soon.`

> [!NOTE]
> The `{{data.firstName}}` syntax references the value your end-user enters in the **First Name** field of the **General Information** module.
10. Connect the output port (right) of the **Signal Start** node to the input port (left) of the **Message** node.
11. Click **X** (Close).

### Configuring the End Node

1. Drag and drop an **End** node in the **Authenticated** swimlane.
2. Click **Edit**.
3. In the **Label** field, enter `Confirmation Email End`.
4. Connect the output port (right) of the **Message** node to the input port (left) of the **End** node.
5. Click **X** (Close).
6. Click **Save...**.
7. Click **Save**.

> [!NOTE]
> Once configured to run, your Signal Start node turns bold in color.

Your completed workflow looks like the following:

[![The completed workflow for sending a confirmation email.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Signal_Start_Complete.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/SignalStart%20node%20example%20complete.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A07%3A27Z&se=2026-10-26T10%3A07%3A27Z&sr=c&sp=r&sig=V513W7K5mULfWi87qaZ8Wbt5khxP%2B2kvvWvk0IkV9KE%3D)

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.