---
title: "Workflow Builder"
slug: "workflow-builder"
tags: ["workflow-builder"]
status: "update"
updated: 2026-10-13T18:21:22Z
published: 2026-10-13T18:21:22Z
canonical: "docs.unqork.io/workflow-builder"
---

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

# Workflow Builder

The Workflow Builder is a visual Business Process Model and Notation (BPMN)-style editor for building automated, trigger-based workflows. Use it to model multi-step business processes by connecting nodes on a canvas, like document review, user onboarding, or automated notifications.

Workflows run independently of modules. They execute in response to triggers, move data through a series of tasks, and can interact with modules, external systems, and other workflows.

## Key Concepts

### Nodes

Nodes are the building blocks of a workflow. Each node represents a specific step—starting the workflow, executing a task, routing logic, sending a message, or ending the process. Connect nodes with links to define the order of execution.

### Links

Links are the connections between nodes. On gateway nodes, links carry conditions that determine which the workflow follows at runtime.

### Swimlanes

Swimlanes are horizontal divisions in the workflow canvas. Use swimlanes to assign sections of a workflow to specific roles, controlling which end-users have access to which tasks.

### Sub-Processes

A Sub-Process node groups a set of nodes into a collapsible container. Use Sub-Process nodes to organize complex workflows into logical sections and to apply swimlane-based access control to a group of tasks.

## How Workflows Are Triggered

Workflows begin from one of three Start node types:

- **[Start node](/unqorkai/docs/start-node)**: The default entry point. A workflow with a Start node runs when manually launched or called from another workflow.
- **[Timer Start node](/unqorkai/docs/timer-start-node)**: Begins a workflow automatically on a schedule. Supports relative, exact, and cron-based timing.
- **[Signal Start node](/unqorkai/docs/signal-start-node)**: Begins a workflow automatically when a specific platform event fires, like when an application is promoted or a module is saved.

A workflow can have multiple Start nodes. Use the **Set as Default Start** setting to define which one runs by default.

## Views

The Workflow Builder toolbar includes a **Definition** drop-down for switching between views. Click **Definition** and select a view.

| View | Description |
| --- | --- |
| **Definition** | The main canvas for building and editing the workflow. |
| **Transforms** | Create and manage data transform templates. See [Transforms](/unqorkai/docs/transforms-1). |
| **Translations** | Add locales and manage translated text strings. See [Translations](/unqorkai/docs/translations-1). |
| **History** | Browse, preview, and restore saved versions of the workflow. See [Version History](/unqorkai/docs/version-history-workflow-builder). |

## Toolbar

The Workflow Builder toolbar includes an ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_182120_04d33d4a1f9941aa9ee9f0905152e2e4.svg?sv=2026-02-06&spr=https&st=2026-11-08T10%3A17%3A53Z&se=2026-11-08T11%3A17%3A53Z&sr=c&sp=r&sig=PC6FKIMT5jrgTCpeCN3G%2BRXAhklIl9KaedCQdY%2F2NEA%3D) (**ellipsis**) menu with the following options.

| Option | Description |
| --- | --- |
| **Modify Workflow** | Expands to **Copy Workflow** and **Paste Workflow**. Copy saves the current workflow definition to the clipboard. Paste replaces the current workflow with a copied definition. A confirmation dialog opens before the paste completes. |
| **Grid Snapping** | Toggles grid snapping on or off. When on, nodes snap to a grid when repositioned on the canvas. |
| **Settings** | Opens the [Workflow Settings](/unqorkai/docs/workflow-settings-1) dialog for configuring workflow identity, end-user navigation, canvas layout, custom messaging, save-and-exit behavior, and display options. Also accessible from the Explorer ellipsis next to the workflow. |

## How Workflows Execute

Once triggered, the workflow engine moves through connected nodes in sequence. At gateway nodes, the engine evaluates conditions on output links to determine which path to follow. [Task nodes](/unqorkai/docs/task-node) execute modules—either automatically (Service and Script tasks) or by presenting a module to an end-user as a step in the workflow (User tasks).

Workflows can pause at [Timer nodes](/unqorkai/docs/timer-node), hand off submissions to other workflows through the [Handoff node](/unqorkai/docs/handoff-node), or trigger other workflows through the [Signal node](/unqorkai/docs/signal-node).

---

**Changelog**

| Date | Change |
| --- | --- |
| — | Initial publication. |

Triggers activate another component when certain requirements are met. Trigger types include Concurrent, Post, and Error. Some components do not have the ability to trigger others.

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.

A string is an object that represents a sequence of characters. Strings typically hold data represented in text form.

A place on your operating system that stores recently copied content. The clipboard only stores one item at a time.

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.