Human Node

A human node ("type": "human") pauses the workflow and waits for a person. It has a single handler class, human_task. Use this page when building nodes for Create a Workflow or Update a Workflow. A case that reaches a human node moves to the WAITING status until the task is completed — see Get Case Status.

Process Fields

string

required

What the person needs to do. This is the entire process object — a human task has no model, no prompts and no tools.Write it for the person who will open the task, not for Opus. What the task takes in and hands back is defined by the node’s input_schema and output_schema instead — see Variable Schemas.

Example

human node

{
  "id": "{NODE_ID}",
  "name": "Approve Refund",
  "type": "human",
  "handler_class": "human_task",
  "process": {
    "instructions": "Review the refund request and the attached receipt. Approve if the amount matches the receipt and the request is within 30 days of purchase; otherwise reject with a reason."
  }
}

Whether a human task is carried out inside Opus or somewhere else is a design-view setting, not a process field, and it cannot be set through the create or update endpoints. Configure it in the Builder.

Human Tasks

How human tasks appear and behave in the Opus product

Review Tasks

Human and agentic review steps

Get Started

Workflows

Cases

Files

Business Process Discovery

Integrations

Agents

Deprecated

Process Fields

Example

Human Tasks

Review Tasks

​Process Fields

​Example

​Related

Human Tasks

Review Tasks

Process Fields

Example

Related