} 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:
{{ variableName }}
You can embed expressions in a larger string:
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 |
|---|---|
| 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 |
|---|---|
| The unique ID of the current submission. |
| The ID of the end-user associated with the current submission. |
| Properties from the authenticated user's session. See currentUser Object for available properties. |
Global Variables
Global variables configured in the environment are accessed using the vars prefix.
Expression | Description |
|---|---|
| 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 | Back Button Label |
|
Task | Next Button Label |
|
Sub-Process | Label |
|
Message | To |
|
Message | Refer String Redirect Target |
|
Notes
Template expressions are processed on the server.
If a referenced variable is
nullorundefined, 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. |