Humain

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.

Formulaire rapide

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.

	Formulaire rapide	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	Oui (Yes)
Coût	No additional units, no Apps dependency	Requires app deployment
Mise en page	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
Test	Inline debug from canvas	Build → deploy → run
Build skills required	Aucun (None)	App Studio, or React/Angular for coded Apps

Astuce :

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.

Configuration

Champ	Requis	Default	Description
Assignment criteria	Oui (Yes)	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.
Schéma	Oui (Yes)	Soumettre le résultat	Form structure, including fields the assignee sees or fills in and outcomes they can select. Refer to Schema for the full structure.
Canaux de livraison	—	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.
Titre de la tâche	Non (No)	Aucun (None)	Titre affiché pour le bénéficiaire dans sa liste de tâches.
Priorité (Priority)	Non (No)	Aucun (None)	Priorité affichée dans Action Center: Faible, Moyenne ou Élevée.
Libellés	Non (No)	Aucun (None)	Des libellés séparés par des virgules pour organiser les tâches, par exemple 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ères	Who gets the task	Utilisez-le lorsque
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
Personnalisé	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.

Exigences et limites

Important :

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:

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

Schéma

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

Champs

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:

Paramètre	Ce qu’il fait
Label	The display name shown to the assignee.
Saisie de texte	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.
Modifiable	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

Les champs transportent des données dans et hors de la tâche. Chaque champ a une direction.

• Les champs d'entrée sont en lecture seule pour le contexte de la personne affectée, liés à une valeur de processus, par exemple $vars.start.output.employeeName.
• Les champs de sortie sont remplis par la personne affectée et renvoyés au processus.
• Les champs Entrée/Sortie font les deux: ils affichent pour le bénéficiaire une valeur de processus comme point de départ, et le bénéficiaire peut la modifier avant qu'elle ne soit renvoyée au processus.

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
Ensemble	Locked 🔒	Entrée	The bound value	Non (No)
Ensemble	Unlocked 🔓	Entrée/Sortie	The bound value	Oui (Yes)
Aucun (None)	Unlocked 🔓	Sortie	An empty field	Oui (Yes)
Aucun (None)	Locked 🔒	Not valid	An empty field	Non (No)

Résultats

Les résultats sont les boutons que le bénéficiaire utilise pour terminer la tâche, par exemple Approuver et Rejeter. Le schéma par défaut a un seul résultat Soumettre . Le premier résultat est marqué comme action principale.

Chaque résultat ajoute sa propre gestion de sortie au nœud. Lorsque le bénéficiaire sélectionne un résultat, le processus se poursuit à partir du contrôle de ce résultat, vous permettant d’acheminer chaque résultat vers un chemin différent. Référez-vous à Brancher sur le résultat.

Delivery channels

Tasks are delivered to:

• Action Center
• E-mail (Email)
• Slack
• Microsoft Teams

Important :

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.

Sortie

Accédez à la sortie du nœud au niveau de $vars.<nodeName>.output et au résultat sélectionné au niveau de $vars.<nodeName>.status.

sortie

Le résultat de la tâche: un objet contenant les valeurs soumises par le bénéficiaire, clés par champ de sortie. Lire un seul champ avec $vars.<nodeName>.output.<fieldId>. L’objet comporte également une propriété Action définie sur le résultat sélectionné.

statut

Le résultat sélectionné par le bénéficiaire, par exemple Approve. Branchez-vous sur cette valeur pour acheminer le processus.

Ramification sur le résultat

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

Lisez un champ soumis dans n'importe quel nœud en aval avec $vars.<nodeName>.output.<fieldId>:

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

Le résultat sélectionné est également disponible en tant que $vars.<nodeName>.status si vous en avez besoin dans une expression.

Problèmes couramment rencontrés

La tâche n’apparaît pas pour le bénéficiaire

Vérifiez que le bénéficiaire, qu’il s’agisse d’un utilisateur ou d’un groupe, est correct et a accès à Action Center.

An output value is missing

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

Un résultat mène au chemin incorrect

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.

Remarques

Remarque :

Pour tester sans bénéficiaire réel, utilisez la sortie simulée pour simuler une réponse status et output . Référez-vous à la section Ajouter une approbation humaine à un workflow pour connaître les étapes.

• Si le bénéficiaire est un groupe, tout membre de ce groupe peut demander et terminer la tâche.
• For a richer interface than a form, back the task with an Action app instead of a Quick form.

Pages liées

• Ajouter une approbation humaine à un workflow
• Décision
• Terminate
• Tâches de formulaire rapides