Copilot Studio: Add Human Review When AI Decisions Need Oversight
Diesen Beitrag auf Deutsch lesen
Build a Copilot Studio workflow that checks loan purposes, requests human input through Outlook or Teams, and records the decision in SharePoint.
TL;DR
A Copilot Studio workflow compares a loan purpose with a SharePoint list, assigns Allowed, Flagged, or Human-Review, and pauses for an Outlook or Teams response when no matching purpose exists. The workflow then updates the loan application with the decision, review status, and rationale.
Original by Matthew Devaney, on Matthew Devaney. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Add an agent node with structured category output so workflows can separate Allowed, Flagged, and Human-Review cases.
- Makers: Configure the Human Review action with reviewer inputs for a yes or no decision and rationale.
- Admins/IT: Watch the Outlook or Teams review channel and SharePoint fields because the workflow depends on the reviewer response before continuing.
Frequently asked questions
How does a Copilot Studio workflow decide when a loan application needs human review?
The workflow assigns Human-Review when the stated loan purpose has no matching entry in the supplied SharePoint Loan Purposes list.
Which channels can Copilot Studio use to request a reviewer decision?
The Human Review action can contact a reviewer through Outlook email or Teams chat, then wait for the submitted response.
How does Copilot Studio store a human reviewer’s loan decision and rationale?
The workflow updates SharePoint with the Allowed or Flagged decision, a human-review status, and the reviewer’s rationale.