maestro

latest

false

Maestro user guide

Human Task

The Human Task node pauses the process and assigns a task to a person, then resumes once they complete it. Use it when a process needs human review, approval, or input before it can continue.

This page covers the Quick form task type, where you build the form directly on the node. For a hands-on walkthrough, refer to Add human approval to a workflow.

When to use Human Task vs Decision

Use the Human Task node when a person needs to review information and respond before the process continues. Use the Decision node when the branch can be resolved automatically from existing data, without human involvement.

The Human Task node routes on the assignee's chosen outcome through its own output handles. Reach for a Decision when the branch follows from existing data instead of a person's choice.

Task types

The Type field controls how the task is presented to the assignee.

Quick form

Build the form directly on the node. You define the fields the assignee sees and the outcomes they can choose. This is the default and the best fit for approvals and straightforward data collection. The rest of this page documents Quick form.

Custom app

Back the task with a coded Action App for a richer, custom interface. Select the app under Action App and map its inputs. Building the app itself is covered in the Action Apps documentation.

Configuration

Field	Required	Default	Description
Type	Yes	Quick Form	Task presentation mode. Quick Form presents a form defined on the node; Custom App presents a coded Action App.
Delivery Channels	Yes	Action Center and email, assigned to a group	Task delivery destinations and assignee. Supported channels are Action Center, Email, Slack, and Microsoft Teams; Slack and Microsoft Teams require an Integration Service connection.
Task Schema	Yes	Submit outcome	Form structure, including fields the assignee sees or fills in and outcomes they can select. Refer to Schema: fields and outcomes for the full structure.
Task title	No	None	Title shown to the assignee in their task list.
Priority	No	None	Priority shown in Action Center: Low, Medium, or High.
Labels	No	None	Comma-separated labels for organizing tasks, for example `finance,approval`.

Schema: fields and outcomes

The Task Schema defines what the assignee sees and what they return to the process. It has two parts: fields and outcomes.

Fields

Fields carry data into and out of the task. Each field has a direction.

Input fields are read-only context for the assignee, bound to a process value, for example $vars.start.output.employeeName.
Output fields are filled in by the assignee and returned to the process.
In/Out fields do both: they show the assignee a process value as a starting point, and the assignee can edit it before it's returned to the process.

Each field has a type. Available types:

text
number
date
boolean
file

Outcomes

Outcomes are the buttons the assignee uses to complete the task, for example Approve and Reject. The default schema has a single Submit outcome. The first outcome is marked as the primary action.

Each outcome adds its own output handle to the node. When the assignee selects an outcome, the process continues from that outcome's handle, so you can route each outcome to a different path. Refer to Branching on the result.

Output

Access the node's output at $vars.<nodeName>.output and the selected outcome at $vars.<nodeName>.status.

output

The task result: an object holding the values the assignee submitted, keyed by output field. Read a single field with $vars.<nodeName>.output.<fieldId>. The object also carries an Action property set to the selected outcome.

status

The outcome the assignee selected, for example Approve. Branch on this value to route the process.

Branching on the result

Each outcome you define adds an output handle to the Human Task node. When the assignee completes the task, the process continues from the handle for the outcome they selected. Connect each outcome handle to the node that should run for that path. You don't need a Decision node to split on the outcome.

Human Task
  ├─ Approve → continue processing
  └─ Reject  → notify the requester and terminate
Human Task
  ├─ Approve → continue processing
  └─ Reject  → notify the requester and terminate

Read a submitted field in any downstream node with $vars.<nodeName>.output.<fieldId>:

// In a Script node on one of the outcome paths
return $vars.approval.output.comment;
// In a Script node on one of the outcome paths
return $vars.approval.output.comment;

The selected outcome is also available as $vars.<nodeName>.status if you need it in an expression.

Common issues

Task does not appear for the assignee

Verify the assignee, whether a user or a group, is correct and has access to Action Center.

An output value is missing from output

Confirm the field is defined in the Task Schema with direction Output.

An outcome routes to the wrong path

Confirm each outcome's output handle is connected to the node you intend. Each outcome you define in the schema has its own handle on the Human Task node.

Notes

Note:

To test without a real assignee, use Mock output to simulate a status and output response. Refer to Add human approval to a workflow for the steps.

If the assignee is a group, any member of that group can claim and complete the task.
For a richer interface than a form, set Type to Custom App and back the task with an Action App.

Was this page helpful?

PREVIOUSAPI Workflow

NEXTDocument processing

Maestro user guide

When to use Human Task vs Decision​

Task types​

Quick form​

Custom app​

Configuration​

Schema: fields and outcomes​

Fields​

Outcomes​

Output​

output​

status​

Branching on the result​

Common issues​

Task does not appear for the assignee​

An output value is missing from output​

An outcome routes to the wrong path​

Notes​

Related pages​