back to worker quest hub

power automate flow build sheet

Generated: 2026-06-29

Use this after SharePoint Lists/forms are live. These flows connect the RaveFocus worker hub, SharePoint Lists, and Planner dispatch/mirror plans.

source records

• Planner dispatch map: outputs/planner-master-task-system-map.json
• Planner task export: outputs/planner-master-task-system-tasks.csv
• SharePoint manual list schema: outputs/sharepoint-list-manual-setup.csv
• SharePoint unblock runbook: outputs/sharepoint-live-setup-unblock-runbook.md

flow 1 - task request to planner

Trigger:

• SharePoint List: task requests
• Event: when an item is created or modified

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/bucket from outputs/planner-master-task-system-tasks.csv.
• If an existing task title matches in the target plan/bucket, update the SharePoint item with the Planner task link.
• If no matching task exists and approval allows creation, create a Planner task.
• Write back:
• - related planner task link
• - approval status
• - blocked reason if missing required data

Safety:

• Do not create tasks from unapproved custom pricing, money, legal, compliance, recovery, access, or payout requests.
• Route those to approval requests.

flow 2 - proof submission review

Trigger:

• SharePoint List: proof submissions
• Event: when an item is created

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 task with proof link in safe notes/checklist where allowed.
• Set task status label or percent complete according to review status.
• If proof is accepted, move/mark task for pay review.
• If proof needs correction, create or update a correction task visible only to the assigned worker/admin.

Safety:

• If sensitive proof is needed, store only owner-only private record required.
• Do not paste private fan/customer info, ID photos, billing, bank, payout, passwords, or recovery details into Planner.

flow 3 - approval request routing

Trigger:

• SharePoint List: approval requests
• Event: when an item is created or modified

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.
• If approved, write the written approval link back to the related task/list item.
• If rejected, write safe rejection reason and blocked reason.

Safety:

• Restricted items should not be sent to general worker channels.

flow 4 - content scheduling approval

Trigger:

• SharePoint List: content scheduling
• Event: when an item is created or modified

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 with proof/status.
• Mark calendar updated as yes only when the calendar proof exists.

Safety:

• Custom pricing, sponsor commitments, restricted content, or creator safety uncertainty must route to Jupiter first.

flow 5 - lenslab edit handoff

Trigger:

• SharePoint Lists: edit request intake, edited content handoffs, edit review + revisions, final export + delivery
• Event: when an item is created or approval status changes

Actions:

• Route edit requests to the matching LensLab Planner plan.
• Require raw folder link and edit brief before starting.
• Send revision items back as correction tasks.
• Record final handoff link.

Safety:

• Do not expose unrestricted content vault access.
• Use only assigned folders and proof-safe links.

flow 6 - lineup booking proof

Trigger:

• SharePoint List: booking intake
• Event: when an item is created or modified

Actions:

• Map booking records to the lineup - bookings + pop-ups Planner plan.
• Update calendar proof, venue proof, call time proof, run-of-show proof, and completion proof.
• Escalate major reschedules, cancellations, sponsor commitments, venue agreement approvals, and payment/deposit uncertainty to Jupiter.

Safety:

• Payment/deposit status should be confirmed with Jupiter or an owner-only payment record.
• Do not upload billing, card, bank, payout, or private payment details to Planner.

flow 7 - echo safe crm shift summary

Trigger:

• SharePoint Lists: shift submissions, fan crm safe index, sales log
• Event: when an item is created

Actions:

• Route Echo shift proof to admin review.
• Update safe CRM tags and follow-up status.
• Send boundary risk, custom possible, private/sensitive, delivery needed, or needs Jupiter review tags to Jupiter/admin.

Safety:

• Do not store private fan/customer records in the worker hub.
• Use only safe CRM summaries and owner-only private record flags.

flow 8 - signal analytics report

Trigger:

• SharePoint Lists: performance log, content winners, analytics reports
• Event: when an item is created or report status changes

Actions:

• Route analytics tasks to Signal or Hello fallback.
• Require metric source link, date range, and report link.
• Update related Planner task and dashboard/report status.

Safety:

• Numbers without source proof are not accepted.
• Private customer/fan records should not be included.

flow 9 - pay review gate

Trigger:

• SharePoint Lists: proof submissions, pay review
• Event: when proof review status changes to approved

Actions:

• Create/update pay review row.
• Keep worker earnings private.
• Mark completed tasks out of worker-facing access after proof approval.
• If sent back, create a private correction task instead of republishing completed work.

Safety:

• no proof = no payout
• no assigned task = not payable
• no approved task order or written approval = not payable
• no public leaderboard earnings