# Build a workflow process

Create a workflow process in a project, drop a trigger and actions onto the designer, connect them and set each one up. Worked example: file every uploaded document into a Customer/Year folder and rename it from its Invoice Number and Vendor.

Product: nucleus-one · Audience: catalog-administrator · Time: 20 minutes · Last verified: 2026-11-20

Canonical: https://help.ademero.com/nucleus-one/using-nucleus-one/build-a-workflow-process

**At the end of this guide you'll have a working process in your project: every uploaded document is filed into a folder built from its field values and renamed from two more, with no one touching it.**

A process has three parts. A **trigger** starts it (a document was uploaded, a form was submitted). **Actions** do the work (move the document, rename it, email someone, start an approval). **Connections** join them: the trigger's output to the first action, that action's output to the next. You draw all three on one canvas, the designer.

## Create the process

1. In the project, open **Settings** > **Workflow Processes** and click **+**. Only project administrators see **Settings**.
2. In **Create a workflow process**, type a **Name** and click **CREATE**. The designer opens. (Click the name at the top later to rename it; click a process's card under **Workflow Processes** to reopen it.)

## Find your way around the designer

The **Toolbox** on the left lists **Triggers** and **Actions**. The rest of the screen is the canvas.

- **Add an element:** drag it from the Toolbox onto the canvas. The first time, an **Adding elements** tutorial plays; the Toolbox's menu (the three dots) replays it any time.
- **Connect two elements:** point at the first element. Orange arrows appear on it: **Input** at the top, **Output** at the bottom. Drag from its **Output** arrow to the next element. Nothing can connect into a trigger.
- **Set up an element:** point at it and click the green gear (**Settings**) at its top edge. Every settings dialog has a **Name** (the label on the canvas) and ends with **CLOSE** and **SAVE**.
- **Remove an element:** point at it and click the red trash can (**Delete**) at its bottom edge, or select it and press Delete. Confirm **Delete element(s)?**

*[Screenshot: The process designer with the Toolbox on the left (Triggers and Actions lists) and a Document upload trigger connected to a Folder change action on the canvas, with the gear, info and trash can icons showing on the pointed-at action.]*

There's no Save, Publish or Enable button. Every drop, connection and **SAVE** is stored as you go, and a process works as soon as a trigger is connected to an action. The designer shows a warning while something is unfinished:

| Warning | Meaning |
| --- | --- |
| **No connected triggers** | Nothing will start the process yet. Connect a trigger to an action. |
| **1 incomplete element** (or more) | An element shown in red is missing a required setting. Open its **Settings** and fill it in. |
| **1 invalid connection due to property conflict** | Two connected elements' settings contradict each other. Change one of them. |

### Side ports on approvals and tasks

Most actions have one **Input** (top) and one **Output** (bottom). Three have extra connection points on their sides. Point at a port to see its name.

| Action | Port | Where | What you connect to it |
| --- | --- | --- | --- |
| **Approval**, **Group Approval** | **Approve** | Bottom | The next step when the document is approved |
| **Approval**, **Group Approval** | **Decline** | Left | The next step when it is declined, so each decision can lead somewhere different |
| **Approval**, **Group Approval** | **Arrival Notification Override** | Right | An **E-mail** action: your own message replaces the default notification sent when the approval arrives |
| **Task** | **Output** | Bottom | The next step |
| **Task** | **Reminder Notification Override** | Left | An **E-mail** action: your own message replaces the default reminder |
| **Task** | **Arrival Notification Override** | Right | An **E-mail** action: your own message replaces the default notification sent when the task arrives |

The two override ports accept only an **E-mail** action; the designer refuses any other connection. Leave them unconnected to keep the default notifications. A connection drawn from a side port is labeled **Decline**, **Notify** or **Remind** on the canvas.

## Worked example: file and rename every upload

Your project has four fields: **Customer**, **Year**, **Invoice Number** and **Vendor**. You want each uploaded document filed under `Customer/Year` and named `Invoice Number - Vendor`.

1. Drag **Document upload** from **Triggers** onto the canvas. Leave its settings as they are, so it covers every upload. (**Filter by document folder** would limit it to uploads into one folder, with **Include subfolders** as an option.)
2. Drag **Folder change** from **Actions** below it, and connect the trigger's **Output** to it.
3. Open the Folder change **Settings**. Each row is one folder level. In the first row set **Type** to **Field value** and **Field** to **Customer**.
4. Click **+** (**Add item**) for a second row: **Field value**, **Year**. A preview above the rows shows the path, `/Customer/Year`. Click **SAVE**.
5. Drag **Document rename** below Folder change and connect Folder change's **Output** to it.
6. Open its **Settings** and build the name from three rows: **Field value** > **Invoice Number**; then **Text** > ` - ` (space, hyphen, space); then **Field value** > **Vendor**. The preview reads `Invoice Number - Vendor.extension`. Click **SAVE**.

*[Screenshot: The Folder change settings dialog with two rows, both Type Field value, set to Customer and Year, and the bold path preview /Customer/Year above them.]*

There are no tokens to type. You build a path or a name by stacking rows, and each row's **Type** is **Text**, **Field value**, **Asset tag** or **All text tags in alphabetical order**. The trash can beside a row (**Remove item**) deletes it.

What happens when it runs, for a PDF with Customer `Northwind Traders`, Year `2026`, Invoice Number `INV-1001` and Vendor `Acme Supply`:

- It's filed in `Northwind Traders` > `2026`. Folders that don't exist yet are created, starting from the top of the project's folders.
- It's renamed `INV-1001 - Acme Supply.pdf`. **The original file extension is always kept.** You never add it yourself.
- Field values in a name are separated by a space automatically, unless a **Text** row sits between them. That's why the ` - ` row works.

> **IMPORTANT:** **Document upload** runs once, as soon as the uploaded file finishes processing, and both actions read the field values the document has at that moment. A field with no value becomes a folder named `_No value_` and is left out of the name. That suits documents that arrive with their field values already set, for example from a capture source that sends them. If people fill in the fields after uploading, start the process with a **Document fields commit** trigger instead. It runs each time a document's field values are saved, and files and renames the document then. A folder a process created is removed when a move leaves it empty.

For a date field, set **Length** to **Partial length** and pick a **Date part** such as **Year, YYYY**; a text field's **Partial length** takes a **Characters** count. Folder change's **Share with people (optional)** shares the destination folder with the people you list.

*[Screenshot: The finished example on the canvas: Document upload connected to Folder change, connected to Document rename, with no warnings showing.]*

**Success check:** upload a test PDF that has all four field values (or upload it, fill in the fields and save, if you used the **Document fields commit** trigger). Within a few minutes it should appear in `Customer/Year` with its new name.

## Every trigger

| Trigger | Starts the process when |
| --- | --- |
| **Asset completion** | An asset item is completed. Filter by asset, field values and tags. |
| **Document fields commit** | A document's field values are saved. Filter by field values, tags and folder. |
| **Document recycled** | A document is sent to the recycle bin. Filter by folder. |
| **Document upload** | An uploaded document finishes processing. Filter by folder. |
| **Form submit** | A form is submitted. Filter by form template and its field values. |
| **Item accept** | A document or asset is handed over by an **Item release** action. Connects only to **Asset** or **Document from source**. |
| **New asset** | A new asset item is created. Filter by asset, field values and tags. |
| **Schedule by field** | A date field on a document or asset is reached, shifted by an offset **Before** or **After** it. |
| **Tags update** | An item's tags change. Filter by tags. |
| **Task completion** | A task is completed. Filter by who it was assigned to, and tags. |

## Every action

| Action | What it does |
| --- | --- |
| **Approval** | Assigns an approval to one person. **Approve** and **Decline** each lead to their own next step. |
| **Group Approval** | Assigns an approval to several people; you choose whether any, all or a majority must take part. |
| **Asset** | Creates an asset item from what reached it, with field values you set. |
| **Document from source** | Creates a copy of the incoming document in this project, with tags you add. |
| **Document from template** | Creates a new document from a document template you choose. |
| **Document rename** | Renames the document from text, field values, asset tags or tags, keeping its extension. |
| **E-mail** | Sends an email with a **Subject** and **Body** to the people in **To** and **CC**; it can attach the document. |
| **Folder change** | Files the document into a folder path built from text, field values, asset tags or tags. |
| **Form share** | Shares a form template with the people you list. |
| **Item release** | Hands a document or asset to an **Item accept** trigger, optionally limited to the fields you allow to transfer. |
| **Send to recycle bin** | Sends the item to the recycle bin. No settings. |
| **Restore from recycle bin** | Restores the item from the recycle bin. No settings. |
| **Task** | Creates a task assigned to a person; it can send reminders and notifications. |

## When a process didn't run

- **Is the trigger connected?** A **No connected triggers** warning means nothing will start it.
- **Is anything red?** Open each red element's **Settings** and complete it.
- **Did it land in `_No value_`?** The fields were empty when the trigger ran. See the important note above.
- **Is the trigger filtered?** Open the trigger's **Settings** and check **Filter by document folder**: an upload into another folder won't start it.

Still stuck? Contact support with the project name, the process name, the document's name, roughly when it was uploaded, and what you expected to happen compared with what did.

## What's next

- [Build and submit forms](https://help.ademero.com/nucleus-one/using-nucleus-one/build-and-submit-forms)
- [Find anything with advanced search](https://help.ademero.com/nucleus-one/using-nucleus-one/find-anything-with-advanced-search)
