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.

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

	Formulario 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	Sí
Coste	No additional units, no Apps dependency	Requires app deployment
Diseño	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
Pruebas	Inline debug from canvas	Build → deploy → run
Build skills required	Ninguno	App Studio, or React/Angular for coded Apps

Consejo:

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.

Configuración

Campo	Obligatorio	Predeterminado	Descripción
Assignment criteria	Sí	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	Sí	Enviar resultado	Form structure, including fields the assignee sees or fills in and outcomes they can select. Refer to Schema for the full structure.
Canales 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 de tarea	No	Ninguno	Título que se muestra al asignado en su lista de tareas.
Prioridad	No	Ninguno	Prioridad mostrada en Action Center: Baja, Media o Alta.
Etiquetas	No	Ninguno	Etiquetas separadas por comas para organizar tareas, por ejemplo 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.

Criterios	Who gets the task	Úsalo cuando
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
Personalizar	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 y límites

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:

Error	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:

Configuración	Lo que hace
Etiqueta	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.
Editable	The padlock next to the value. Locked means the assignee can read the value but not change it.
Variable	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

Los campos transportan datos dentro y fuera de la tarea. Cada campo tiene una dirección.

• Los campos de entrada son contexto de solo lectura para el usuario asignado, vinculados a un valor de proceso, por ejemplo $vars.start.output.employeeName.
• Los campos de salida son rellenados por el usuario asignado y devueltos al proceso.
• Los campos de entrada/salida hacen ambas cosas: muestran al destinatario un valor de proceso como punto de partida, y el destinatario puede editarlo antes de que se devuelva al proceso.

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	Dirección	Assignee sees	Editable & returned
ESTABLECER	Locked 🔒	Entrada	The bound value	No
ESTABLECER	Unlocked 🔓	In/Out	The bound value	Sí
Ninguno	Unlocked 🔓	Salida	An empty field	Sí
Ninguno	Locked 🔒	Not valid	An empty field	No

Resultados

Los resultados son los botones que utiliza el usuario asignado para completar la tarea, por ejemplo Aprobar y Rechazar. El esquema predeterminado tiene un único resultado Enviar . El primer resultado se marca como la acción principal.

Cada resultado añade su propio identificador de salida al nodo. Cuando el usuario asignado selecciona un resultado, el proceso continúa desde el identificador de ese resultado, para que puedas enrutar cada resultado a una ruta diferente. Consulta Ramificar en el resultado.

Delivery channels

Tasks are delivered to:

• Action Center
• Correo electrónico
• 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.

Salida

Accede a la salida del nodo en $vars.<nodeName>.output y al resultado seleccionado en $vars.<nodeName>.status.

salida

El resultado de la tarea: un objeto que contiene los valores que el usuario asignado envió, introducidos por el campo de salida. Leer un solo campo con $vars.<nodeName>.output.<fieldId>. El objeto también lleva una propiedad Action establecida en el resultado seleccionado.

estado

El resultado seleccionado por el usuario asignado, por ejemplo Approve. Ramifica en este valor para enrutar el proceso.

Ramificación en el 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

Leer un campo enviado en cualquier nodo posterior con $vars.<nodeName>.output.<fieldId>:

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

El resultado seleccionado también está disponible como $vars.<nodeName>.status si lo necesitas en una expresión.

Problemas comunes

La tarea no aparece para el usuario asignado

Verifique que el asignado, ya sea un usuario o un grupo, sea correcto y tenga acceso a Action Center.

An output value is missing

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

Un resultado redirige a la ruta incorrecta

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.

Notas

Nota:

Para probar sin un asignado real, utiliza Salida simulada para simular una respuesta status y output . Consulta Añadir aprobación humana a un flujo de trabajo para ver los pasos.

• Si el asignado es un grupo, cualquier miembro de ese grupo puede reclamar y completar la tarea.
• For a richer interface than a form, back the task with an Action app instead of a Quick form.

Páginas relacionadas

• Añadir aprobación humana a un flujo de trabajo
• Decisión
• Terminate
• Tareas de formulario rápido