人間

Human node for pausing a process and assigning a task for human review, approval, or input.

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

When to use Human vs Decision

Use the Human 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 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.

Human node types

The task presented to the human can be created via two mechanisms: Quick form and Action app.

クイック フォーム

Build and debug a lightweight form directly on the node. You define the fields the assignee sees, the inputs they need to provide and the outcomes they can choose. This is the default and the best fit for approvals and straightforward data collection.

Action app

Action apps provide a richer, fully customized interface for the task assigned to the human. They can be built visually in UiPath App Studio or Studio Web, or as a Coded Action App—a custom React or Angular application. A coded app is selected under Action App, and its inputs are mapped at configuration time. Refer to About Coded Action Apps.

	クイック フォーム	Action app
UI defined	On the node, versioned with the process	Separate app, deployed to Orchestrator
Reuse across processes	Yes, by copying and pasting JSON	はい
コスト	No additional units, no Apps dependency	Requires app deployment
レイアウト	Allows multi-column, multi-width layouts, Field behavior	Full control
Data at render time	Bound process variables/expressions only	SDK: assets, buckets, connections, Data Fabric, trigger processes
テスト	Inline debug from canvas	Build → deploy → run
Build skills required	なし	App Studio, or React/Angular for coded Apps

ヒント:

Start with a Quick form. Move to an Action app when you need to reuse the same interface across processes, show data the process does not already carry, or build a UI a form cannot express.

Building the app itself is covered in the Action Apps documentation. From this point onward, this page covers the Quick form task type. For a hands-on walkthrough, refer to Add human approval to a workflow.

構成

フィールド	Required	既定 (Default)	説明
Assignment criteria	はい	Single User	Controls how the Human node picks the person who gets the task. Choose between Single User, All users, Round Robin, Workload, or Custom.
スキーマ	はい	結果の送信	Form structure, including fields the assignee sees or fills in and outcomes they can select. Refer to Schema for the full structure.
配信チャネル	—	Set at tenant level	Read-only on the node — the available channels are inherited from tenant-level configuration and shown as disabled checkboxes. Refer to Delivery channels for details.
タスク タイトル	いいえ	なし	タスク リスト内の担当者に表示されるタイトル。
優先度	いいえ	なし	Action Center に表示される優先度は、 低、 中、 高です。
ラベル	いいえ	なし	タスクを整理するためのコンマ区切りのラベル (例: finance,approval)。

Assignment criteria

Assignment criteria controls which person or people receive the task. Selecting a criterion changes the second field to match — a user picker for Single User, a group picker for the group-based criteria.

基準	Who gets the task	次の場合に使用します
Single User	One named person.	A specific individual owns this decision — a named approver, a single reviewer
All users	Every member of the group at once. The first person to complete it closes the task for everyone.	You care about speed over ownership. Whoever is free picks it up
Workload	The one group member with the fewest open tasks	You want the queue spread evenly across a team
Round Robin	Group members in turn, cycling through the membership list	You want each member to take an equal share regardless of how fast they work
カスタム	The member with the fewest open tasks, chosen from a list of users you supply at runtime rather than from a group's full membership.	Eligibility changes per run — skipping people who are out of office, off shift, or outside the right role or region.

要件と制限事項

重要:

Workload and Round Robin require a local group. Active Directory groups are rejected for both. Use Single User or All users if your assignees are in an Active Directory (AD) group.

In debug, group assignment does not work from a personal workspace. Debug runs create the task in your personal workspace, which group members cannot access — so the task is created but stays Unassigned, and no notifications go out. This is expected, not a defect. Deploy the solution to a shared folder to test group assignment properly. Single-user assignment works normally in debug.

Errors you may see:

Error	意味
NoUsersFoundInLocalGroup	The selected group has no members.
NoEligibleUsersFoundInGroup	Every member was excluded, so there is nobody left to assign to.

スキーマ

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

フィールド

The Schema can also be edited directly as JSON. Refer to Quick Form tasks for the full JSON schema reference. In the Form view, each field has these settings:

設定	機能
ラベル	The display name shown to the assignee.
入力	Controls validation and how the input renders. Available types: Text, Number, Decimal number, Date, Date and time, Yes or no, Single select, Multi-select, Array, File.
Binding	An expression that pre-populates the field, for example $vars.requestAmt. Accepts any workflow expression, not only a variable reference.
編集可能	The padlock next to the value. Locked means the assignee can read the value but not change it.
変数	Shown as an (x) badge next to the field name. Auto-derived from the Label for Output and In/Out fields, exposing the value as a named process variable in addition to $vars.<nodeName>.output.<fieldId>. Not present on Input fields.

Field directions

フィールドは、タスクに出入りするデータを運びます。各フィールドには方向があります。

• 入力 フィールドは担当者の読み取り専用のコンテキストであり、プロセスの値 (例: $vars.start.output.employeeName) にバインドされます。
• 出力 フィールドは担当者によって入力され、プロセスに返されます。
• 入力/出力 フィールドは、その両方を行います。つまり、担当者にプロセスの値を出発点として表示し、担当者はその値を編集してからプロセスに戻すことができます。

A field's direction is not a separate setting. It is the result of two controls: whether the field is bound determines if it arrives pre-filled, and whether it is unlocked determines if the assignee can change it.

Binding	Padlock	方向	Assignee sees	Editable & returned
Set	Locked 🔒	入力	The bound value	いいえ
Set	Unlocked 🔓	入力/出力	The bound value	はい
なし	Unlocked 🔓	出力	An empty field	はい
なし	Locked 🔒	Not valid	An empty field	いいえ

結果

結果は、担当者がタスクを完了するために使用するボタンです ( 例: 承認 、 却下)。既定のスキーマでは、[ 送信 ] の結果が 1 つになります。最初の結果がプライマリ アクションとしてマークされます。

各結果は、独自の出力ハンドルをノードに追加します。担当者が結果を選択すると、プロセスはその結果のハンドルから続行されるため、各結果を異なるパスにルーティングできます。「 結果の分岐」を参照してください。

Delivery channels

Tasks are delivered to:

• Action Center
• メール
• Slack
• Microsoft Teams

重要:

Delivery channels can only be modified at the tenant level, from Admin settings. The checkboxes on the node are disabled and reflect the current tenant configuration.

Slack and Microsoft Teams require an Integration Service connection. Refer to Actionable notifications for connector setup.

出力

ノードの出力に $vars.<nodeName>.output でアクセスし、選択した結果に $vars.<nodeName>.statusでアクセスします。

出力

タスクの結果: 担当者が送信した値を保持するオブジェクトです。キーは出力フィールドで設定されます。$vars.<nodeName>.output.<fieldId>で 1 つのフィールドを読み込みます。このオブジェクトには、選択した結果に設定された Action プロパティも含まれます。

ステータス

担当者が選択した結果です (例: Approve)。この値で分岐してプロセスをルーティングします。

結果に対する分岐

Each outcome you define adds an output handle to the Human 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
  ├─ Approve → continue processing
  └─ Reject  → notify the requester and terminate

送信済みフィールドを任意の下流ノードで読み取る $vars.<nodeName>.output.<fieldId>

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

選択した結果は、式で必要な場合は $vars.<nodeName>.status としても使用できます。

一般的な問題

担当者のタスクが表示されない

担当者が正しいか (ユーザーかグループか) であり、Action Center へのアクセス権を持っていることを確認します。

An output value is missing

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

結果が間違ったパスにルーティングされる

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

備考

注:

実際の担当者なしでテストするには、[ モック] 出力 を使用して status と output 応答をシミュレートします。手順については、「 ワークフローに人間による承認を追加する 」をご覧ください。

• 担当者がグループの場合、そのグループのメンバーは誰でもタスクを要求して完了できます。
• For a richer interface than a form, back the task with an Action app instead of a Quick form.

関連ページ

• ワークフローに人間による承認を追加する
• 判断
• Terminate
• クイック フォーム タスク