Add human approval to a workflow

What you'll build: A process that pauses at a review step, sends an approval task to a designated person, and continues on the correct path once they respond, approved or rejected. This pattern is the building block for any process that requires a human sign-off before proceeding.

This guide uses the Quick Form task type, where you build the approval form directly on the Human Task node.

Éléments requis

• A UiPath Automation Cloud account with access to Maestro Flow.

Nodes used

• Manual Trigger: starts the process on demand
• Human Task: pauses execution and creates an approval task for the assigned approver
• Terminate: ends the rejected path cleanly

Étapes

1. Build the pre-approval steps

First, set up the nodes that run before the approval point. Create a new flow and add the nodes that fetch or receive the data the approver needs to review, then transform it into a readable format.

2. Add a Human Task node

Add the node that creates the approval task and pauses the process.

1. Drag a Human Task node from the UiPath nodes section onto the canvas.
2. Connect it to the last pre-approval node.
3. In the properties panel, configure the task:
   • Type: leave set to Quick Form.
   • Task Delivery: review the admin-configured channels where the task is delivered, such as Action Center or Slack.
   • Assignment criteria: set the approver as a single user, a variable-based custom assignment, or a group assignment strategy such as round robin or workload distribution.
   • Schema: define the form. Add input fields for the read-only context the approver reviews (for example, the invoice amount, the requester name, and a link to the supporting document), each bound to a process value such as $vars.manualTrigger1.output["amount"]. For this scenario, add two outcomes: Approve and Reject.
   • Priority: set to High if the task is time-sensitive.

3. Branch on the approver's response

The Human Task node has one output handle per outcome you defined, so you route each outcome directly.

1. Connect the Approve outcome handle to the continuation of your process (for example, a system write or a notification).
2. Connect the Reject outcome handle to a Terminate node to end that path cleanly.

4. Test and debug

You don't need a real approver to test this flow. Choose one of the following approaches.

• Run in debug without mocking: Debug the flow and let it reach the Human Task node. This creates a real task that you can complete inline, without leaving the debugger, so you can verify both the Approve and Reject branches using the actual task experience.
• Use Mock output: Simulate a response instead of completing a task.
  1. Select the Human Task node and open Mock output in the properties panel.
  2. Enable the mock toggle.
  3. Set status to Approve (or Reject to test the rejection branch).
  4. Debug the flow and verify the correct branch executes.
  5. Remove the mock before publishing.

Résultat

Your process pauses at the Human Task node, sends the approval form to the designated person, and routes execution on the correct path once they respond. The approved path continues the automation; the rejected path terminates cleanly.

Extend this flow

• Notify the approver: before the Human Task node, add a notification step (email or Slack) to tell the approver that a task is waiting.
• Escalate on rejection: on the Reject path, instead of terminating immediately, invoke an Agent or route to a second approver.
• Collect the approver's notes: add an output field to the schema (for example, a comment) and read it after the node with $vars.approval.output.comment.