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.
The problem
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.
Meeting Analytics & Recap (Google Workspace)
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Intermediate · Setup time: 30–60 minutes
🧩 Based on the prebuilt skill
Clone-Meeting-Analytics-Google. You attach it; you don't have to write it.
1. Overview and value
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.
2. Who it's for
Customer Success and Sales teams who want fast, consistent recaps to customers and prospects, and Leadership who want decisions and risks captured.
3. How it works
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 transcriptDry 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.
4. What the clone does (and never does)
Does: emails only invitees of the locked event, sends once, records the ledger. Never: guesses recipients, emails anyone not on the event, sends when matching is ambiguous, or sends a meeting twice.
5. Setup walkthrough
- Hand CLONE-INSTRUCTIONS.md to your clone: "Set this up. Show me a plan first."
- Review discovery and answer the placeholders.
- Approve the plan: the clone attaches Clone-Meeting-Analytics-Google.
- Connect Google (sign-in) and confirm or create the knowledge base.
- Run a DRY RUN and inspect recipients and the email.
- Only then create the hourly schedule with "Run meeting analytics".
6. Placeholders to decide
| Placeholder | Meaning | Example |
|---|---|---|
{MEETING_KB} | Knowledge base for the ledger | Meeting Analytics KB |
{NOTES_FOLDER} | Drive folder name | Meet Recordings |
{RUN_SCHEDULE} | Schedule and time zone | Hourly, 7 AM to 7 PM, Mon–Fri |
{BRAND_NAME} | Name/branding for the email | Your company |
7. What to expect
After a meeting ends and Gemini notes land in Drive, the next scheduled run emails the attendees. Ambiguous or concurrent meetings are skipped, not guessed.
8. Customizing
Change run frequency, branding or analysis sections, or limit which meetings qualify. Always dry run after changes.
9. 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.
10. FAQ
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.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Nothing sent | No new notes, or ambiguity | Check the folder and calendar; dry run |
| No notes in Drive | Gemini notes off or not organizer | Turn on notes; organize the meeting |
| Duplicate recaps | Another recap system active | Set bot follow-up to owner-only or off |
| Folder not found | Name differs | Name it "Meet Recordings" or tell the clone |
| Repeats | KB write failed | Check KB access |
Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Meeting Analytics & Recap (Google Workspace)
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
>
> 🧩 **Based on the prebuilt skill `Clone-Meeting-Analytics-Google`.** You attach it; you don't have to write it.
---
## 1. Role and goal
Set up the prebuilt skill **Clone-Meeting-Analytics-Google**. When done, you turn Gemini notes into a Meeting Analytics email for the verified attendees of the matching event. Google Workspace only: if the user is on Microsoft 365, say it isn't supported for this card and stop. This is setup only.
## 2. Safety rules
1. Show a numbered plan and wait for an explicit "yes" before attaching, creating or scheduling anything.
2. Never ask for or handle passwords, API keys or tokens.
3. **Never email anyone during setup** except a test to the user, after approval. Attendees (including external) are emailed only by real, approved runs.
4. Manual runs are DRY RUNS: show recipients and the rendered email, send nothing.
5. Use exact catalog names; they can differ slightly between orgs.
## 3. Discovery
Use `platform` and `describeOperator`. Report:
| Item | Status (✅⚠️❌❓) | Exact name in catalog | Notes |
|---|---|---|---|
| Clone-Meeting-Analytics-Google | | | |
| GoogleDriveCoreOperator | | | Folder "Meet Recordings" exists? |
| GoogleDocsCoreOperator | | | |
| GoogleCalendarOperator | | | |
| GoogleGmailOperator | | | |
| Knowledge base (name with "meeting") | | | |
| Scheduled task (platform) | | | |
## 4. Collect placeholders
1. `{MEETING_KB}` (existing or to create)
2. `{NOTES_FOLDER}` (default "Meet Recordings")
3. `{RUN_SCHEDULE}` (default hourly, with time zone)
4. Confirmation that external attendees may be emailed
5. Whether other recap tools exist (meeting bot follow-up)
Confirm in a table before the plan.
## 5. What you can do yourself after approval
- Attach the skill via `platform`.
- Create or confirm the knowledge base via `platform`.
- Run a dry run.
- Create the scheduled task after the user approves the dry run.
If you can't attach it: settings → Skills → **Clone-Meeting-Analytics-Google** → Add → tell me "added".
## 6. What the user must do
1. Connect Google (Drive, Docs, Calendar, Gmail): settings → Connections → Google → sign in.
2. Turn on Gemini notes for Meet in Google Workspace; be the organizer (or notes arrive by email).
3. Set the clone's meeting follow-up to **owner-only or off** so no second recap goes out.
4. Share the knowledge base with the clone if needed.
## 7. Prebuilt skill: configure and run
**What the skill does, step by step:**
1. Find the newest unprocessed Gemini notes in Drive folder "Meet Recordings" (found by name).
2. Dedupe check against the knowledge base ledger.
3. Parse the title datetime and attendee names.
4. Lock the calendar event: start-time window (-5/+20 minutes) plus title match plus attendee overlap. If ambiguous or tied, fail closed.
5. Recipients come only from the locked event's invitees.
6. Safety gate.
7. Analyze: summary, decisions, action items with owners, risks, sentiment, follow-ups.
8. Send once via Gmail.
9. Write three KB records: analytics, "processed" marker, verbatim transcript.
10. Retry a failed call once, then mark it unavailable. Manual runs report it; scheduled runs stay silent on failure.
**Dry run prompt (use first):**
```
Run meeting analytics, dry run, don't send
```
**Scheduled task prompt (hourly, after dry run approval):**
```
Run meeting analytics
```
## 8. Test plan
| Check | ☐ |
|---|---|
| Dry run shows the exact recipients (invitees only) | ☐ |
| Rendered email has all analysis sections | ☐ |
| Nothing was sent during the dry run | ☐ |
| Ambiguous concurrent meetings are skipped | ☐ |
| After an approved real run, one email only; 3 KB records exist | ☐ |
| A second run does not resend | ☐ |
| Hourly schedule listed with the right time zone | ☐ |
## 9. Final status checklist
- ✅ Done by me: skill attached, KB confirmed, dry run, schedule
- ⏳ Waiting on you: Google sign-in, Gemini notes on, follow-up set to owner-only or off, approval to email externals
- 💡 Optional next steps: branding, analysis tweaks, different schedule
Gotchas to repeat: it emails external attendees, so dry run first; never run two recap systems on the same meetings; ambiguous concurrent meetings are skipped by design.
Requirements
Requirements: Meeting Analytics & Recap (Google Workspace)
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 30–60 minutes
🧩 Based on the prebuilt skill
Clone-Meeting-Analytics-Google. You attach it; you don't have to write it.
1. Required skills / operators
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 |
|---|---|---|
| 1 | Clone-Meeting-Analytics-Google (prebuilt skill) | Recap logic |
| 2 | GoogleDriveCoreOperator | Find the "Meet Recordings" folder and notes |
| 3 | GoogleDocsCoreOperator | Read the notes document |
| 4 | GoogleCalendarOperator | Lock the event, read invitees |
| 5 | GoogleGmailOperator | Send the email |
| 6 | A knowledge base (name ideally contains "meeting") | Ledger and records |
| 7 | Scheduled task (platform) | Hourly run |
2. Connections and minimum permissions
| Connection | Minimum permission |
|---|---|
| Google Drive / Docs | Read the notes folder and documents |
| Google Calendar | Read events and invitees |
| Gmail | Send |
| Knowledge base | Read and write |
You sign in yourself. The clone never needs your password.
3. Optional add-ons
| Add-on | Adds |
|---|---|
| Hourly schedule | Hands-free recaps |
| Owner-only follow-up setting | Avoids duplicate recaps from meeting bots |
No CRM mapping applies.
4. Data prerequisites
- Google Workspace with Gemini notes on for Meet
- You are the organizer of meetings (or accept notes via email instead)
- Drive folder named Meet Recordings exists and receives notes
- A knowledge base exists for the ledger
- You are comfortable emailing external attendees
- No other recap system covers the same meetings
5. Roles and permissions
| Role | Needs |
|---|---|
| Meeting organizer | Gemini notes enabled |
| Admin | Can connect Google and create a KB and scheduled task |
6. Estimated setup time
| Task | Time |
|---|---|
| Discovery and placeholders | 10 min |
| Connect Google, confirm KB | 10 min |
| Attach skill, dry run | 10–20 min |
| Schedule | 5 min |
| Total | 30–60 min |
7. Pre-flight checklist
- Gemini notes on
- Google connected
- KB ready
- External emailing approved
- Other recap tools set to owner-only or off
8. You're ready when…
- ✅ The skill is attached
- ✅ A dry run showed the right recipients and email
- ✅ The hourly task "Run meeting analytics" exists
Was this use case helpful?
Thanks!