---
title: "Template Expressions"
slug: "template-expressions"
tags: ["data-integration", "expressions"]
updated: 2026-09-14T17:58:24Z
published: 2026-09-14T17:58:24Z
canonical: "docs.unqork.io/template-expressions"
---

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

# Template Expressions

} syntax in node settings.', }

Some Workflow Builder node settings support template expressions: a way to insert dynamic values directly into text fields using `{{ }}` syntax. Instead of entering a static value, you reference submission data, system values, or global variables that are resolved at runtime.

## Syntax

Template expressions use double curly braces around a variable name:

```plaintext
{{ variableName }}
```

You can embed expressions in a larger string:

```plaintext
Hello {{ data.firstName }}, your submission ID is {{ submissionId }}.
```

## Available Variables

### Submission Data

Access any field value from the current submission using its Property ID.

| Expression | Description |
| --- | --- |
| `{{ data.propertyId }}` | The value of the field with the given Property ID. |

**Example**: If a Text Field component has the Property ID `emailAddress`, use `{{ data.emailAddress }}` to reference its value.

### System Variables

| Expression | Description |
| --- | --- |
| `{{ submissionId }}` | The unique ID of the current submission. |
| `{{ userId }}` | The ID of the end-user associated with the current submission. |
| `{{ currentUser.property }}` | Properties from the authenticated user's session. See [currentUser Object](/unqorkai/docs/currentuser-object) for available properties. |

### Global Variables

Global variables configured in the environment are accessed using the `vars` prefix.

| Expression | Description |
| --- | --- |
| `{{ vars.variableName }}` | The value of a by name. |

## Where Template Expressions Are Supported

Not all node settings support template expressions. Settings that do are noted in their reference pages. Common examples include:

| Node | Setting | Example |
| --- | --- | --- |
| Task | Label | `task-{{ data.caseNumber }}` |
| Task | Back Button Label | `{{ data.previousLabel }}` |
| Task | Next Button Label | `{{ data.nextLabel }}` |
| Sub-Process | Label | `subprocess-{{ data.number }}` |
| Message | To | `{{ data.recipientEmail }}` |
| Message | Refer String Redirect Target | `workflow/path/submission/{{ submissionId }}` |

## Notes

- Template expressions are processed on the server.
- If a referenced variable is `null` or `undefined`, the expression outputs nothing by default. Depending on your environment configuration, it may an error instead.
- Use plain text for fields that don't support expressions. Not all settings accept template expressions.

---

**Changelog**

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

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

A Property ID is the unique field ID used by Unqork to track and link components in your 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.

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.