---
title: "Workflow Submission Fields"
slug: "workflow-submission-fields"
tags: ["workflow-builder"]
status: "update"
updated: 2026-10-13T15:38:06Z
published: 2026-10-13T15:38:06Z
canonical: "docs.unqork.io/workflow-submission-fields"
---

> ## 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 Submission Fields

When a submission moves through a Workflow Builder workflow, Unqork writes workflow metadata directly onto the submission object. These fields are accessible through template expressions and the Submissions API. Use them to build dashboards, filter submission lists, or write conditional logic based on where a submission is in a process.

## Available Fields

| Field | Type | Description |
| --- | --- | --- |
| `__submission__._workflow.state.currentState` | String | The name of the workflow node the submission currently occupies. |
| `__submission__._workflow.state.stateHistory` | Array | The sequence of workflow nodes the submission has passed through, in order. |
| `__submission__.status.current` | String | The current status value on the submission. |
| `__submission__.status.all` | Array | All status values the submission has held, in order. |
| `__submission__._workflow.timerExecutionCounts` | Object | The number of times each timer node has fired for this submission, keyed by node name. |

## Field Details

### `_workflow.state.currentState`

The name of the workflow node the submission currently occupies. Matches the node name as configured in the Workflow Builder.

Use this field to filter a submission list to a specific workflow step. For example, all submissions currently at a "Pending Review" node.

### `_workflow.state.stateHistory`

An array of workflow node names the submission has passed through, from the start node to the current node. Each entry records a transition in the workflow.

Use this field to audit the a submission took through a workflow, identify submissions that passed through a specific node, or calculate how long a submission spent between steps.

### `status.current`

The current status value on the submission. Status values are set by workflow nodes or by direct submission updates.

### `status.all`

An array of all status values the submission has held, in the order they were applied. Use this field to review the full status history of a submission.

### `_workflow.timerExecutionCounts`

An object keyed by timer node name. Each value is the number of times that timer has fired for this submission. A timer node that has fired three times has a count of `3`.

Use this field to build logic that responds to how many times a timer has fired. For example, trigger an escalation after a timer fires a set number of times without resolution.

## Accessing These Fields

These fields are available anywhere template expressions are supported, including module component settings and the List Submissions for Dashboard API.

**In a template expression**:

```
{{__submission__._workflow.state.currentState}}
```

**In a List Submissions for Dashboard query**:

Use the `fields` parameter to include workflow fields in the response. Pass `workflowId` instead of `moduleId` when querying workflow submissions.

```
GET https://{environment}.unqork.io/fbu/uapi/system/getSubmissions?workflowId={workflowId}&fields=__submission__._workflow.state.currentState,__submission__._workflow.state.stateHistory,__submission__.status.current,__submission__.status.all
```

To filter results by workflow state, add the `filter` parameter:

```
GET https://{environment}.unqork.io/fbu/uapi/system/getSubmissions?workflowId={workflowId}&fields=__submission__._workflow.state.currentState&filter={"_workflow.state.currentState":"Pending Review"}
```

To find the `workflowId`, open the workflow in the Workflow Builder. The ID is in the URL:

```
https://{environment}.unqork.io/workflow/{workflowId}
```

## Considerations

- These fields are populated only for submissions that are associated with an active workflow. Submissions not connected to a workflow do not have `_workflow` fields.
- `stateHistory` and `status.all` grow as the submission progresses through the workflow. For long-running processes, these arrays can become large.
- `timerExecutionCounts` only includes timer nodes that have fired at least once. Nodes that have not yet fired do not appear in the object.
- Node names in `currentState` and `stateHistory` reflect the names configured in the Workflow Builder. Renaming a node does not update historical entries in `stateHistory`.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-09-09 | Corrected Submissions API example — updated endpoint to List Submissions for Dashboard, replaced moduleId with workflowId, added fields parameter example, added workflowId location note. |
| 2026-08-31 | Initial publication. |

An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

An array is a type of object that stores one or more data types. Data types supported in arrays include numbers, strings, and objects.

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.

A query lets you retrieve, access, manipulate, and delete data in a database.

A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.

An array is a type of object that stores one or more data types. Data types supported in arrays include numbers, strings, and objects.

An API endpoint is the location where an API receives requests for a specific resource on its server. It's the point of contact between an API client and an API server, and is usually a uniform resource locator (URL) that provides the location of the resource.