Meeting History Extractor
Captures the meeting transcript and stores it in SharePoint as the shared memory every other flow reads.
Use case
Meeting knowledge normally dies inside a Teams recording nobody reopens. This flow lifts the transcript out of the meeting and writes it into a structured SharePoint list, so decisions, owners and context become queryable data instead of a video file.
Who uses it
Project managers, team leads and anyone who chairs recurring meetings.
Real scenario
The Monday project sync ends at 10:00. The chair runs the flow once; by 10:01 the full transcript, meeting title, date and participants are rows in the MeetingHistory list, ready for the agenda and task flows later in the week.
Time saved
Before
~15 min re-listening to the recording and pasting notes into a document
After
0 min — one manual trigger
Time saved
~15 min per meeting
How it works
A manual trigger collects the meeting title, date and transcript text. A Compose action normalises line breaks, and Create item writes a single record to the SharePoint MeetingHistory list, which becomes the foundation every downstream Meeting Autopilot flow reads from.
Step-by-step build
- 1
Create a SharePoint list named MeetingHistory with columns: Title (single line), MeetingDate (date and time), Participants (multiple lines), Transcript (multiple lines, plain text), Source (choice: Teams / Manual).
- 2
In Power Automate create a new Instant cloud flow and choose the trigger 'Manually trigger a flow'.
- 3
Add trigger inputs: Text 'MeetingTitle', Date 'MeetingDate', Text 'Participants', Text 'Transcript'.
- 4
Add a Data Operation → Compose action named 'NormalisedTranscript' with the expression replace(triggerBody()['text_3'], decodeUriComponent('%0D%0A'), decodeUriComponent('%0A')).
- 5
Add the SharePoint connector action 'Create item', pointing at your site and the MeetingHistory list.
- 6
Map Title, MeetingDate and Participants from the trigger inputs, Transcript from the Compose output, and set Source to Manual.
- 7
Add a Notifications action 'Send me a mobile notification' (or Office 365 Outlook → Send an email V2) confirming the item ID that was created.
- 8
Save, then run once with a real transcript and verify the item appears in the list with line breaks intact.
Copilot prompt
Paste this into Power Automate Copilot to scaffold the flow.
Create an instant cloud flow triggered manually with text inputs for MeetingTitle, Participants and Transcript and a date input for MeetingDate. Normalise the transcript line breaks with a Compose action, then create an item in the SharePoint list 'MeetingHistory' on my site mapping Title, MeetingDate, Participants and Transcript, and finally send me a confirmation notification with the new item ID.
Screenshots
Captures are added as each step is published.
Official documentation
Explore more flows
Pre-Meeting Agenda Injector
Fifteen minutes before a meeting starts, it writes a full HTML agenda directly into the Outlook invite.
View module LiveTask Extraction from Transcript
Turns pipe-delimited transcript lines into assigned Planner tasks with real Azure AD owners.
View module LiveDaily Activity Log Email
Every weekday at 18:20 Rome time it logs the day's Planner activity and drafts the team lead's summary email.
View module LiveWeekly Status Report
Builds done / overdue / in-progress tables, posts them to Teams and archives a CSV in SharePoint.
View module LiveDeadline Urgency Monitor
A daily 08:00 Teams digest that colour-codes every approaching deadline — and stays silent at weekends.
View module LiveColumn Name Monitor
Hourly SharePoint schema watchdog that catches renamed columns before they silently break every flow.
View module