Pipeline Report
Weekly pipeline snapshot by stage and owner, posted to Teams with a CSV archived in SharePoint.
This flow is being documented
Architecture and use case are already public. Build instructions and screenshots follow as the flow is finalised.
Use case
Pipeline numbers are rebuilt by hand every week from the same source. Automating the snapshot makes the trend line reliable because it is always measured the same way.
Who uses it
Sales managers and operations.
Real scenario
Monday 08:00: Teams shows total pipeline value by stage, week-over-week movement and the top ten deals by value, with a CSV archived for the trend history.
Time saved
Before
~60 min per week rebuilding the report
After
0 min — it is waiting on Monday morning
Time saved
~60 min per week
How it works
A Monday recurrence aggregates the opportunity list by stage and owner, compares against the previous snapshot stored in SharePoint, builds HTML tables with deltas and posts them to Teams while archiving the CSV.
Step-by-step build
- 1
Weekly recurrence on Monday at 08:00 in the local timezone.
- 2
Get all open opportunities and aggregate value by stage and by owner.
- 3
Read last week's snapshot from SharePoint to compute deltas.
- 4
Build HTML tables including week-over-week movement and the top ten deals.
- 5
Post to the sales Teams channel and archive both the snapshot and a CSV in SharePoint.
Copilot prompt
Paste this into Power Automate Copilot to scaffold the flow.
Create a scheduled flow that runs every Monday at 08:00, reads all open opportunities from SharePoint, aggregates value by stage and by owner, compares the totals with last week's stored snapshot to compute deltas, posts HTML tables with week-over-week movement and the top ten deals to a Teams channel, and archives the snapshot and a CSV file in SharePoint.
Screenshots
Captures are added as each step is published.