Lesson 17.3: Building a Simple Approval Workflow

Module 17: Copilot + Power Automate Workflows

Lesson 17.3: Building a Simple Approval Workflow

Intermediate Last verified: 2026-06-02
Availability and governance note: Power Automate flows depend on connectors, environments, licenses, permissions, DLP policies, app approvals, service accounts, and tenant governance.

Lesson Promise

Design an approval flow with clear trigger, approver, decision, notification, and audit trail.

Real-World Scenario

A marketing team wants campaign requests submitted by form, reviewed by a manager, and then routed to a planner if approved.

Core Concept

Approvals are one of the strongest beginner automation patterns because they keep human decision-making visible.

A good approval flow defines request fields, approver, approval type, timeout, notification, outcome, and audit needs.

Copilot can help draft flow logic and approval messages, but a human should review business rules before launch.

Step-By-Step Workflow

  1. Define the request intake source.
  2. List required fields and validation rules.
  3. Choose approver, approval type, and timeout or escalation behavior.
  4. Define approved and rejected branches.
  5. Send clear notifications to requestor and next owner.
  6. Test submitted, approved, rejected, missing-data, and no-response cases.

Prompt Lab

Bad Prompt

Create an approval flow.

Better Prompt

When a campaign request form is submitted, send approval to the marketing manager, then notify the requestor and planner based on the result.

Expert Prompt

Design a Power Automate approval workflow for campaign requests. Include trigger, required fields, validation, approval type, approver, timeout, escalation, approved branch, rejected branch, notifications, audit trail, failure handling, DLP concerns, and test cases.

Hands-On Exercise

Create the blueprint for a simple approval flow.

Deliverable

An approval workflow blueprint with test cases.

Automation Safety Checklist

Common Mistakes

  • Automating a broken process instead of simplifying it first.
  • Skipping exception paths, retries, and failure notifications.
  • Moving sensitive data through connectors without checking DLP and permissions.
  • Creating approval flows without clear approvers, timeouts, and audit expectations.
  • Leaving a flow ownerless after launch.
Pro tip: Automate the handoff, reminder, routing, or record update before automating judgment. The fastest safe wins usually remove coordination friction while humans keep decision authority.

Quiz / Checkpoint

Why are approvals a good automation pattern?

They automate routing and records while preserving human decision authority and an audit trail.

Official Sources To Verify

For AI founders and marketers

Want your AI product explained to a large AI-native audience?

Kingy AI helps AI companies turn complex products into clear, useful YouTube videos that drive awareness, product understanding, demos, clicks, and search visibility.