Power Automate workflow · Creative ops

Creative request intake, Frame.io / PDF review and approval

Marketing requests go to a queue, designers get a brief, reviewers comment on PDFs or Frame.io links, and approvals are logged.

TriggerMicrosoft Forms — creative request
ConnectorsMicrosoft Forms · Planner · Microsoft Teams · Approvals · SharePoint
CategoryCreative ops

The problem

Design requests arrive through WhatsApp and email with no brief; feedback is scattered across chats.

The outcome

Every request has a brief, owner, due date and a single review thread.

Before you start

  • A Creative Requests Planner plan and a review library.

Build it step by step

  1. Brief — Capture channel, sizes, copy, languages (EN/BM/中文) and deadline.
  2. Assign — Create a Planner task with the brief in the description.
  3. Review — Designer uploads the PDF proof or shares a Frame.io link; the flow posts it in Teams for comments.
  4. Approve — Start and wait for an approval with the brand owner.
  5. Deliver — Approved assets move to the brand library with tags.

Connector action names are shown as they appear in Power Automate at the time of writing; Microsoft and Adobe occasionally rename actions or add new versions.

Error handling

  • Set a maximum of 3 review rounds and escalate after that.

Licensing

  • Standard connectors; Creative Cloud for designers; Frame.io included with Creative Cloud Pro plans.

Variations

  • Generate first-draft variations with Firefly before the designer starts.

Common in: Retail · Hospitality · Banking