RaveFocus Power Automate setup

Power Automate owner action sheet

After SharePoint Lists exist, build the nine Power Automate flows, capture actual flow IDs and URLs, then rerun postsetup and final preflight.

9 flows to build

0/9 IDs captured

0/9 URLs captured

0/15 worker Lists verified

52 ID rows missing

4 preflight blockers

Do not make flows live yet. Build and capture only after SharePoint Lists are verified; flows must write proof-safe links and statuses only.

open json download csv open post-setup check

Guardrails

do not create flows against missing SharePoint Lists
do not switch flows live until trigger Lists, ID capture, reconciliation, and final preflight pass
flows must write proof-safe links and status only
no proof = no payout
no assigned task = not payable
do not put passwords, recovery codes, ID photos, payment details, payout settings, private fan/customer records, or private creator records into flows

1 manual capture required

task request to planner

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: task requests - when an item is created or modified
Planner/List targets: website-compatible Planner dispatch/mirror plans
Conditions: approval status is submitted or approved; requested planner bucket is present; requested task title is present; duplicate task check is not duplicate
Actions: find matching Planner plan and bucket; reuse existing task if plan/bucket/title already exists; create Planner task only when approval allows; write back Planner task link, approval status, and blocked reason
Safety: route money/legal/compliance/recovery/access/payout/custom pricing to approval requests
Blocked until: SharePoint trigger Lists are created and verified

2 manual capture required

proof submission review

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: proof submissions - when an item is created
Planner/List targets: related Planner task, pay review queue
Conditions: assigned planner task link exists; proof link exists; proof matches assigned task is yes or needs correction
Actions: notify Jupiter/admin review queue; update Planner proof link or safe checklist note; move accepted proof to pay review; create private correction task when proof needs correction
Safety: sensitive proof becomes owner-only private record required
Blocked until: SharePoint trigger Lists are created and verified

3 manual capture required

approval request routing

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: approval requests, blocker + escalation log - when an item is created or modified
Planner/List targets: jupiter approval + restricted review, related task/list item
Conditions: approval type involves money, legal, compliance, access/security, sponsor commitment, custom pricing, recovery, payout, restricted content, or owner-only decision
Actions: notify Jupiter/admin only; update jupiter review; update approval status; write approval link back when approved; write safe rejection/block reason when rejected
Safety: restricted items do not go to general worker channels
Blocked until: SharePoint trigger Lists are created and verified

4 manual capture required

content scheduling approval

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: content scheduling - when an item is created or modified
Planner/List targets: content scheduling + approvals, related Planner task
Conditions: approval status changes to approved; calendar updated is not yes
Actions: notify assigned role owner; update calendar tracker/manual calendar task; update related Planner task proof/status; set calendar updated to yes only after proof exists
Safety: sponsor commitments, restricted content, creator safety uncertainty, or custom pricing route to Jupiter first
Blocked until: SharePoint trigger Lists are created and verified

5 manual capture required

lenslab edit handoff

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: raw asset intake, edit request intake, edited content handoffs, edit review + revisions, final export + delivery - when an item is created or approval status changes
Planner/List targets: lenslab editing pipeline
Conditions: raw folder link exists before work starts; edit brief exists before work starts
Actions: route edit request to LensLab Planner plan; send revisions back as correction tasks; record final handoff link; update approval status
Safety: use only assigned folders and proof-safe links; do not expose unrestricted content vault access
Blocked until: SharePoint trigger Lists are created and verified

6 manual capture required

lineup booking proof

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: booking intake - when an item is created or modified
Planner/List targets: lineup bookings + pop-ups
Conditions: booking type exists; date/location or blocker reason exists
Actions: map booking records to Lineup Planner plan; update calendar, venue, call time, run-of-show, and completion proof; escalate major reschedules/cancellations/sponsor or venue approval/payment uncertainty to Jupiter
Safety: confirm payment/deposit status with Jupiter or owner-only payment record; do not upload billing/card/bank/payout/private payment details
Blocked until: SharePoint trigger Lists are created and verified

7 manual capture required

echo safe crm shift summary

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: shift submissions, fan crm safe index, client + creator follow-up, sales log - when an item is created
Planner/List targets: echo chatter + safe crm, admin review
Conditions: shift summary or safe CRM index update exists
Actions: route Echo shift proof to admin review; update safe CRM tags and follow-up status; send boundary/custom/private/sensitive/Jupiter-review items to admin
Safety: do not store private fan/customer records in worker hub
Blocked until: SharePoint trigger Lists are created and verified

8 manual capture required

signal analytics report

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: performance log, content winners, analytics reports - when an item is created or report status changes
Planner/List targets: signal analytics + reports
Conditions: metric source link exists; date range exists; report link or summary exists
Actions: route analytics tasks to Signal or Hello fallback; update related Planner task; update dashboard/report status
Safety: numbers without source proof are not accepted; private customer/fan records should not be included
Blocked until: SharePoint trigger Lists are created and verified

9 manual capture required

pay review gate

build this Power Automate flow only after the trigger Lists exist, then paste the actual flow id and flow url into the capture columns

Capture columns: actual flow id | actual flow url | test run proof link
Trigger: proof submissions, pay review - when proof review status changes to approved
Planner/List targets: pay review, admin-only completed archive
Conditions: proof review status is approved; assigned task or approved written order exists
Actions: create or update pay review row; keep worker earnings private; remove completed tasks from worker-facing access; create private correction task if sent back
Safety: no public leaderboard earnings; no bank/card/payout details
Blocked until: SharePoint trigger Lists are created and verified