MEETINGS & PRODUCTIVITYBuilt on Clone Meeting Analytics Google

Meeting Analytics & Recap (Google Workspace)

Gemini notes from Google Meet become a polished analytics email to the verified attendees, sent once, with a knowledge base ledger.

A prebuilt skill finds the newest unprocessed Gemini notes in your Meet Recordings Drive folder, locks the matching calendar event (time window, title and attendee overlap), fails closed on ambiguity, emails the verified attendees a branded analysis (summary, decisions, action items with owners, risks, sentiment, follow-ups), then records analytics, a processed marker and the transcript to a knowledge base so nothing is sent twice. Manual runs are dry runs.

At a glance

Difficulty
Intermediate
Setup time
30–60 min
Built for
Customer Success, Sales, Leadership
Start freeBook a Demo

Version 1.0.0 · updated 2026-10-22

Overview

The problem it solves

Meeting notes pile up unsent and unanalyzed. Follow-ups are late, action items lack owners, and manual recaps get duplicated or sent to the wrong people.

Google Meet with Gemini notes produces a notes document in Drive. This skill turns each one into a branded Meeting Analytics email and sends it to the verified attendees of the matching calendar event (internal and external, by design). It then writes three records to a knowledge base so the meeting is never sent twice.

The email contains: summary, decisions, action items with owners, risks, sentiment and follow-ups.

Google only. Microsoft 365 is not supported for this card.

Who it’s for

Customer SuccessSalesLeadership

Customer Success and Sales teams who want fast, consistent recaps to customers and prospects, and Leadership who want decisions and risks captured.

How it works

code
 Gemini notes in Drive folder "Meet Recordings" (found by name)
   │
   ▼  newest unprocessed notes
 Dedupe check (knowledge base ledger)
   ▼
 Parse title datetime and attendee names
   ▼
 Lock the calendar event:
   start-time window (-5/+20 min) + title match + attendee overlap
   ▼  ambiguity or tie? fail closed (skip)
 Recipients = invitees of the locked event only
   ▼
 Safety gate ► Analyze ► Send once via Gmail
   ▼
 Write 3 KB records: analytics · "processed" marker · verbatim transcript

Dry run: manual runs are dry runs by default (or say "dry run, don't send"): you see the exact recipients and the rendered email, and nothing is sent. Scheduled runs (for example hourly) are silent on failure.

Setup, step by step

  1. Hand CLONE-INSTRUCTIONS.md to your clone: "Set this upShow me a plan first."
  2. Review discovery and answer the placeholders
  3. Approve the plan: the clone attaches Clone Meeting Analytics Google
  4. Connect Google (sign-in) and confirm or create the knowledge base
  5. Run a DRY RUN and inspect recipients and the email
  6. Only then create the hourly schedule with "Run meeting analytics"

The full walkthrough is in the README. The Clone Instructions file tells your clone exactly what to do.

What you’ll need

Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

#Skill / operator (exact name)Used for
1Clone Meeting Analytics Google (prebuilt skill)Recap logic
2Google Drive Core OperatorFind the "Meet Recordings" folder and notes
3Google Docs Core OperatorRead the notes document
4Google Calendar OperatorLock the event, read invitees
5Google Gmail OperatorSend the email
6A knowledge base (name ideally contains "meeting")Ledger and records
7Scheduled task (platform)Hourly run

Known gotchas

  • It emails EXTERNAL attendees. Confirm that is wanted and dry run first.
  • Gemini notes must be on. You should be the meeting organizer, or the notes arrive by email instead of in your Drive.
  • Never run two recap systems on the same meetings (for example a meeting bot's follow-up plus this). Set the clone's meeting follow-up to owner-only or off.
  • Ambiguous concurrent meetings are skipped by design.
  • Google only.

Questions

Does it work with Outlook or Teams?

No, Google only.

Can I preview?

Yes, dry run.

Why was a meeting skipped?

Ambiguity, already processed, or no matching event.

Will it send twice?

No, the ledger marker prevents it.

Ready to set up Meeting Analytics & Recap (Google Workspace)?
Your clone shows you a plan before it changes anything.