Meeting recaps that send themselves, once, to the right people
Your clone turns Google Meet notes into a polished recap email for the people who were actually there.
When Gemini notes from a Google Meet land in Drive, your clone matches them to the right calendar event, checks who attended, and emails them a recap with decisions, owners, risks and follow-ups. It records each meeting in a knowledge base so nothing is sent twice. Google Workspace only.
What your clone does
Meeting notes pile up unsent, follow-ups are late, and manual recaps go to the wrong people. Your clone sends one accurate recap per meeting.
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 helps
Customer Success and Sales teams who want fast, consistent recaps to customers and prospects, and Leadership who want decisions and risks captured.
How it runs
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.
Set it up, step by step
- Hand CLONE-INSTRUCTIONS.md to your clone: "Set this upShow 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"
The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.
Before you start
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 | Google Drive Core Operator | Find the "Meet Recordings" folder and notes |
| 3 | Google Docs Core Operator | Read the notes document |
| 4 | Google Calendar Operator | Lock the event, read invitees |
| 5 | Google Gmail Operator | Send the email |
| 6 | A knowledge base (name ideally contains "meeting") | Ledger and records |
| 7 | Scheduled task (platform) | Hourly run |
Good to know
- 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, answered
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 when you are. So is your clone.
Build your clone, paste in the Meeting Analytics & Recap (Google Workspace) instructions, and approve the plan it shows you.