Humano

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.

Formulário rápido

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.

	Formulário rápido	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	Sim
Custo	No additional units, no Apps dependency	Requires app deployment
Layout	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
Teste	Inline debug from canvas	Build → deploy → run
Build skills required	Nenhum	App Studio, or React/Angular for coded Apps

Dica:

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.

Configuração

Campo	Required	Padrão	Description
Assignment criteria	Sim	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.
Esquema	Sim	Enviar resultado	Form structure, including fields the assignee sees or fills in and outcomes they can select. Refer to Schema for the full structure.
Canais de entrega	—	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.
Título da Tarefa	Não	Nenhum	Título mostrado para o destinatário na sua lista de tarefas.
Prioridade	Não	Nenhum	Prioridade exibida no Action Center: Baixa, Média ou Alta.
Rótulos	Não	Nenhum	Rótulos separados por vírgulas para organizar tarefas, por 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.

Critérios	Who gets the task	Use-o ao
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
Personalizado	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.

Requisitos e limites

Importante:

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:

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

Esquema

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

Campos

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:

Configuração	O que faz
Label	The display name shown to the assignee.
Tipo	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.
Editável	The padlock next to the value. Locked means the assignee can read the value but not change it.
Variável	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

Os campos carregam dados para dentro e para fora da tarefa. Cada campo tem uma direção.

• Os campos de entrada são contexto somente leitura para o destinatário, associados a um valor de processo, por $vars.start.output.employeeName.
• Os campos de saída são preenchidos pelo destinatário e retornados ao processo.
• Os campos In/Out fazem as duas coisas: eles mostram ao destinatário um valor de processo como um ponto de partida, e o destinatário pode editá-lo antes que ele retorne ao processo.

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	Direction	Assignee sees	Editable & returned
DEFINIR	Locked 🔒	Entrada	The bound value	Não
DEFINIR	Unlocked 🔓	In/Out	The bound value	Sim
Nenhum	Unlocked 🔓	Saída	An empty field	Sim
Nenhum	Locked 🔒	Not valid	An empty field	Não

Resultados

Resultados são os botões que o destinatário usa para concluir a tarefa, por exemplo, Aprovar e Rejeitar. O esquema padrão tem um único resultado de Enviar . O primeiro resultado é marcado como a ação principal.

Cada resultado adiciona seu próprio identificador de saída ao nó. Quando o destinatário seleciona um resultado, o processo continua a partir do identificador desse resultado, para que você possa rotear cada resultado para um caminho diferente. Consulte Ramificação no resultado.

Delivery channels

Tasks are delivered to:

• Action Center
• Email
• Slack
• Microsoft Teams

Importante:

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.

Saída

Acesse a saída do nó em $vars.<nodeName>.output e o resultado selecionado em $vars.<nodeName>.status.

saída

O resultado da tarefa: um objeto com os valores que o destinatário enviou, codificados por campo de saída. Leia um único campo com $vars.<nodeName>.output.<fieldId>. O objeto também carrega uma propriedade Action definida para o resultado selecionado.

status

O resultado que o destinatário selecionou, por exemplo Approve Ramifique esse valor para rotear o processo.

Ramificando no resultado

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

Leia um campo enviado em qualquer nó downstream com $vars.<nodeName>.output.<fieldId>:

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

O resultado selecionado também está disponível como $vars.<nodeName>.status se você precisar dele em uma expressão.

Problemas comuns

A tarefa não aparece para o destinatário

Verifique se o destinatário, seja um usuário ou um grupo, está correto e tem acesso ao Action Center.

An output value is missing

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

Um resultado roteia para o caminho errado

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.

Observações

Observação:

Para testar sem um destinatário real, use a saída Simulação para simular uma resposta status e output . Consulte Adicionar aprovação humana a um fluxo de trabalho para ver as etapas.

• Se o destinatário for um grupo, qualquer membro desse grupo pode reivindicar e concluir a tarefa.
• For a richer interface than a form, back the task with an Action app instead of a Quick form.

Páginas relacionadas

• Adicionar aprovação humana a um fluxo de trabalho
• Decisão
• Terminate
• Tarefas de formulário rápido