Before
After a Google Meet, someone likely had to locate the new recording or transcript, identify the related calendar event and attendees, review the content, and write a summary. They then had to look up recipients and distribute the completed notes individually, creating delays and repeated handoffs.
How it works
- Detect a relevant recording-folder update, filter out non-relevant events, and identify the employee and associated file.
- Retrieve the recording or transcript content, extract the meeting title, find the matching calendar event, and collect its attendees.
- Generate a structured summary and send it individually to the identified internal attendees.
Workflow details
- Trigger and triage: The workflow starts when a monitored Meet Recordings folder receives an update. It filters for relevant update events, identifies the associated employee, and retrieves the employee's email address before continuing.
- Recording retrieval: The workflow uses the employee identity to obtain the required access context, locates the newly created file, and retrieves its metadata and content. Depending on the file type, it either downloads the content or exports it as plain text.
- Meeting identification: An AI step extracts the meeting name from the recording file title. The workflow then searches the calendar for the corresponding event and uses the event details to identify the meeting attendees.
- Summary generation: The transcript or chat content is passed to an AI agent that creates a Markdown summary containing the meeting title, attendee names and email addresses, and a concise recap of the discussion.
- Attendee delivery: The workflow looks up each attendee using their email address and sends the completed summary to them individually through Slack, making the meeting recap available without a separate manual distribution process.
What changed
A qualifying recording update now starts the entire process automatically. File retrieval, meeting matching, attendee collection, summary creation, recipient lookup, and Slack delivery happen in sequence, leaving people to review the delivered summary rather than assemble and distribute it themselves.
Work removed
Manually checking recording-folder updates, locating and exporting transcripts, extracting meeting titles, searching calendar events, collecting attendee details, writing meeting summaries, looking up recipients, and sending the recap to each attendee.
Expected outcome
For each qualifying recording, the workflow removes at least one manual transcript-review and summary-writing cycle plus one notification step for each identified attendee.
