--- title: "Signal Start Node" slug: "signal-start-node" tags: ["workflow-builder", "workflow-builder-nodes"] status: "update" updated: 2026-10-13T15:37:15Z published: 2026-10-13T15:37:15Z 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 The Signal Start node begins a workflow automatically when a specific platform event fires—like when an application is promoted or a module is saved. Use it to build event-driven automation without manual triggers. 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 manual starts, see [Start Node](/unqorkai/docs/start-node). For time-based starts, see [Timer Start Node](/unqorkai/docs/timer-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 | `signalStart-{n}` | A display name for the node. | | Path | `nodeId` | Text input | — | The unique identifier automatically generated for the node. Preset and not editable. | | Triggering Event | `triggeringEvent` | Drop-down | — | The platform event that begins this workflow. Options include: **On Promotion (Specific Application)**, **On Promotion (All Applications)**, **On Save (Specific Module)**, **On Save (All Modules)**, **On Save (Specific Workflow)**, **On Save (All Workflows)**. | | ↳ Application | `applicationId` | Module selector | — | The application to monitor for promotion. Visible when **Triggering Event** is **On Promotion (Specific Application)**. | | ↳ Module | `moduleId` | Module selector | — | The module to monitor for saves. Visible when **Triggering Event** is **On Save (Specific Module)**. | | ↳ Workflow | `workflowId` | Module selector | — | The workflow to monitor for saves. Visible when **Triggering Event** is **On Save (Specific Workflow)**. | ## 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. In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module. 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.