Clone Support
Use case

Post-Meeting CRM Autopilot: Meeting Notes → CRM Updates

After every customer or sales meeting, your clone turns the notes into a logged activity, a summary, follow-up tasks and suggested deal updates in Salesforce or HubSpot, after you approve.

The problem

Reps and CSMs finish a call and move straight to the next one. The CRM never gets the notes, next steps live in someone's head, deal fields go stale and forecasts drift. Post-Meeting CRM Autopilot does the data entry for you and keeps you in control of every change.

Post-Meeting CRM Autopilot: Meeting Notes → CRM Updates

Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Intermediate · Setup time: 30–60 minutes

After a customer or sales meeting, your clone reads the notes, works out what happened, and prepares the CRM updates for you: a logged meeting, a summary note, follow-up tasks, contact updates and suggested deal changes. You approve the list, then it writes.


1. Overview and value

Everyone agrees the CRM should be up to date. Nobody has time at 5:45 PM after a day of calls. So notes stay in a doc, next steps stay in someone's head, deal stages go stale and the forecast drifts.

Post-Meeting CRM Autopilot closes that gap. After a meeting, your clone:

  • finds the notes from whichever source exists (its own transcript, AI meeting notes, or notes you paste),
  • extracts the summary, decisions, next steps (owner + due date), deal signals, new contacts and follow-up dates,
  • matches the meeting to the right account, contacts and open deal,
  • shows you a proposed change list and waits for your approval,
  • writes the approved items to Salesforce or HubSpot,
  • optionally emails you a short recap of what was logged.

What you get:

BenefitWhat it looks like
A CRM that is actually currentEvery external meeting is logged with a summary and next steps
No dropped follow-upsNext steps become tasks with owners and due dates
Cleaner forecastsStage, amount and close date changes are suggested from what was said
Time back5–15 minutes of data entry saved per meeting
You stay in controlNothing is written until you approve; deals never move backward or close without your explicit OK

2. Who it's for

  • Sales reps and account executives who want every call logged and every deal field kept honest.
  • Customer Success Managers who need QBR, check-in and escalation calls recorded against the account with clear next steps.
  • RevOps who want consistent activity data and fewer stale opportunities, with a human approval step built in.
  • Sales and CS managers who want pipeline hygiene without nagging the team.

It is built for external meetings (customers, prospects, partners tracked in the CRM). Internal-only meetings are skipped.

3. How it works

code
   Trigger
   ├─ On demand: "Log my last meeting"
   └─ On a schedule (e.g. hourly): any new meetings since last run?
                         │
                         ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  "Post-Meeting CRM Log" skill                                     │
 │                                                                   │
 │  1. Find the meeting + the notes (first source that has them)     │
 │       a) meeting_archive  (clone attended)                        │
 │       b) AI notes in Drive / OneDrive, or emailed notes           │
 │       c) notes you paste in chat                                  │
 │  2. Skip internal-only meetings ({YOUR_COMPANY_DOMAINS})          │
 │     and anything matching {SKIP_RULES}                            │
 │  3. Extract: summary · decisions · next steps (owner, due date)   │
 │       · deal signals · new contacts · follow-up dates             │
 │  4. Match: attendee domain → account → contacts → open deal       │
 │       (several open deals? ask you)                               │
 │  5. Dedupe: "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" exists?│
 │       → skip                                                      │
 │  6. Show the PROPOSED CHANGE LIST                                 │
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
                  You reply "approve" (or edit the list)
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  Write to Salesforce or HubSpot                                   │
 │   · logged meeting/activity + summary note                        │
 │   · follow-up tasks (owner, due date)                             │
 │   · contact updates · new contacts (with confirmation)            │
 │   · deal stage / amount / close date: SUGGESTIONS, applied only   │
 │     on your explicit approval                                     │
 │  Optional: short recap email to you                               │
 └───────────────────────────────────────────────────────────────────┘

Where the notes come from

The clone uses the first source that has notes for the meeting, and tells you which one it used.

SourceWhen it applies
meeting_archiveThe clone attended the meeting and has its own transcript
AI meeting notes in DriveFor example Gemini notes saved in a Google Drive "Meet Recordings" folder (GoogleDriveCoreOperator, GoogleDocsCoreOperator), or the Microsoft 365 equivalent in OneDrive
AI meeting notes by emailNotes emailed to you (found with Gmail or Outlook). Common when you were not the meeting organizer
Pasted notesYou paste notes into chat: "Log this meeting: ..."

How the meeting is matched to the CRM

  1. External attendee email domain → account / company.
  2. Attendees → contacts on that account.
  3. Account → open opportunity / deal. If there is more than one open deal, the clone asks you which one. It never guesses.

4. What the clone does (and never does)

It does, after you approve:

  • logs the meeting as an activity (Salesforce) or engagement meeting (HubSpot), linked to the account, contact and deal,
  • adds a summary note,
  • creates follow-up tasks with owners and due dates,
  • updates contact title and phone when they were clearly stated,
  • creates new contacts only after you confirm each one,
  • suggests deal stage, amount and close date changes.

It never:

  • writes anything before you approve the change list,
  • moves a deal backward, changes an amount, or closes a deal (won or lost) without your explicit approval for that specific change,
  • logs the same meeting twice (it checks for an existing "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" activity first),
  • logs internal-only meetings ({YOUR_COMPANY_DOMAINS}) or meetings matching your {SKIP_RULES},
  • emails customers or prospects,
  • deletes records,
  • asks for your password or tokens.

5. Setup walkthrough

The quickest path: download CLONE-INSTRUCTIONS.md and give it to your clone. It checks what is connected, asks for your settings, shows a plan, and sets up what it can after you approve.

Step 1: Check requirements (5 min). Open REQUIREMENTS.md and run the pre-flight checklist. You need a CRM connection with write access, a place the notes come from, and the ability to create a scheduled task (if you want automation).

Step 2: Hand the instructions to your clone (2 min). Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: "Please set up this use case for me. Show me a plan before changing anything."

Step 3: Review the discovery table (5 min). The clone reports which operators and connections it has and which are missing.

Step 4: Answer the placeholder questions (5 min). See section 6.

Step 5: Approve the plan (2 min). Say "yes" only when it looks right.

Step 6: Do your part (10–20 min). Only you can:

  • Connect your own Salesforce or HubSpot account. Some CRM connections must be finished manually in the integrations settings instead of in chat.
  • Make sure the connection has write access to contacts, companies/accounts, deals/opportunities and activities (admin is not needed).
  • Connect Gmail/Drive or Outlook/OneDrive so the clone can find AI notes (optional).
  • Turn on AI meeting notes in your meeting tool if you want that source.

Step 7: Save the Post-Meeting CRM Log skill (5 min). The clone saves it, or gives you the full text to paste.

Step 8: Run the test plan (10–15 min). Log one test meeting against a test account and check the results.

Step 9: Turn on the schedule (optional). Hourly checks for new meetings, with approval by chat.

6. Placeholders to decide

PlaceholderWhat it meansExample
{CRM_CHOICE}Which CRM you useSalesforce or HubSpot
{YOUR_COMPANY_DOMAINS}Your company's email domains (internal = these)yourcompany.com, yourcompany.io
{NOTES_SOURCE}Where your meeting notes usually liveGemini notes in Drive "Meet Recordings", emailed notes, clone transcript, pasted
{NOTES_FOLDER}Drive or OneDrive folder with AI notes (if used)"Meet Recordings"
{SKIP_RULES}Optional extra meetings to skipTitles containing "1:1" or "Interview"; calendar category "Personal"
{RUN_SCHEDULE}How often the clone checks for new meetings (optional)Hourly, 8 AM–6 PM Mon–Fri, my time zone
{AUTO_LOG_MODE}Optional: auto-write activity + note only (never deal changes)off (default) or on
{RECAP_DELIVERY}How you receive proposals and recapsEmail, Slack, Teams, or chat only
{DEFAULT_TASK_OWNER}Who owns a next step when no owner is statedMe (the CRM user)
{DEFAULT_TASK_DUE_DAYS}Due date when none is stated3 business days

7. What to expect

  • On demand: say "log my last meeting". Within a few minutes you get a proposed change list. Reply "approve" (or edit it) and the clone writes it and confirms.
  • On a schedule: the clone checks for meetings that ended since its last run. If it finds one, it sends you the proposed change list by email or chat and waits for you to reply "approve" before writing anything. It tracks the time of its last run so nothing is processed twice.
  • Auto-log mode (optional): if you turn on {AUTO_LOG_MODE}, the clone writes only the activity and summary note automatically. Deal changes, contact changes, new contacts and tasks always still need approval.
  • Review time: about 1–2 minutes per meeting.

Example proposed change list:

code
Meeting: "Q4 Renewal Check-in" · 2026-10-21 · notes from: meeting_archive
Matched: Account "Example Corp" · Contacts: A. Lee, B. Kim · Deal: "Example Corp Renewal" (only open deal)

1. LOG meeting activity "[Meeting Log] Q4 Renewal Check-in – 2026-10-21"      (no duplicate found)
2. ADD summary note (6 bullets)
3. CREATE tasks
   a. Send revised proposal      · owner: me        · due 2026-10-24
   b. Share security whitepaper  · owner: A. Lee    · due 2026-10-28
4. UPDATE contact A. Lee: title → "VP Operations"  (stated in meeting)
5. NEW contact? "C. Ortiz, Procurement" (needs your confirmation)
6. SUGGESTED deal changes (not applied unless you say so):
   - Close date: 2026-11-30 → 2026-12-15  (customer asked for more time)
   - Risk noted: competitor mentioned
Reply "approve", "approve 1-4", or tell me what to change.

8. Customizing

  • Skip rules. Set {SKIP_RULES} for meetings you never want logged (by title keyword, calendar, or attendee).
  • Note format. Ask for a shorter summary, a template (for example MEDDIC-style fields or a QBR layout), or a different subject prefix.
  • Task defaults. Change {DEFAULT_TASK_OWNER} and {DEFAULT_TASK_DUE_DAYS}.
  • Schedule. Change how often it checks, or run it only on demand.
  • Delivery. Receive proposals and recaps by email, Slack or Teams.
  • Auto-log mode. Turn on activity + note auto-logging after a few weeks of clean approvals. Deal changes always stay manual.

9. Known gotchas

  • Write access is required, admin is not. Your CRM connection needs WRITE access to contacts, companies/accounts, deals/opportunities and activities. It does not need admin rights. People often mix these up and ask for an admin account, or connect with a read-only user and see "permission denied" on the first write.
  • Each user connects their own CRM account. No shared service accounts. Activities and tasks are then attributed to the right person, and the clone only sees what that user can see.
  • Some CRM connections must be finished manually. If the connection does not complete in chat, finish it in the clone's integrations settings (Connections page) and then tell the clone to re-check.
  • Several deals at one company. The clone must ask which deal the meeting belongs to. Pick the right one, or say "none".
  • Transcripts have errors. Names, numbers, prices and dates can be wrong. The clone flags uncertain values, and you should verify amounts, dates and names in the change list before approving.
  • Don't log the same meeting twice. The clone checks for an existing activity titled "[Meeting Log] {Meeting title} – {YYYY-MM-DD}". If you logged it by hand with a different subject, tell it to skip.
  • Notes from meetings you did not organize may arrive by email instead of Drive. AI notes usually land in the organizer's Drive. If you were only an attendee, look in your inbox (the clone checks both).
  • The clone's own transcript only exists if it attended. Otherwise it relies on AI notes or what you paste.
  • Read every instruction before saving the skill. You are responsible for what your clone does.

10. FAQ

Which CRMs work? Salesforce and HubSpot. See the mapping table in REQUIREMENTS.md.

Does it write to the CRM automatically? No. It shows a proposed change list and waits for your approval. The only optional exception is auto-log mode for the activity and summary note, never deal changes.

Can it change my deal stage or amount? It can suggest changes. It only applies them after your explicit approval of that specific change. It never moves a deal backward and never closes a deal without your explicit OK.

What if there are two open deals at the account? It asks you which one.

What if it logs the same meeting twice? It won't. It checks for an existing "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" activity first and skips if found.

Does the clone need to attend my meetings? No. It can use AI meeting notes from Drive or email, or notes you paste. If it does attend (via joinMeeting), it can use its own transcript.

Will it email my customers? No.

Can I use it for internal meetings? No, internal-only meetings are skipped on purpose.

Does it need CRM admin? No. It needs write access to the records it touches, not admin.

Can the whole team use it? Yes, but each person connects their own CRM account and sets up their own clone or runs their own schedule.

11. Troubleshooting

SymptomLikely causeFix
"Permission denied" when writingConnection is read-only or missing write access to one objectReconnect with write access to contacts, companies/accounts, deals/opportunities and activities (admin not needed)
CRM connection won't finish in chatSome connections must be completed in settingsFinish it on the clone's Connections / Integrations page, then ask the clone to re-check
No notes foundNotes in a different folder or sent by email; clone did not attendTell the clone where to look, check your inbox, or paste the notes
Wrong account matchedPersonal email domain, shared domain or missing domain on the accountCorrect the match in the change list; add the domain to the account
Clone asks which dealMore than one open deal at the accountPick the right one
Meeting skippedInternal-only, matched {SKIP_RULES}, or already loggedCheck the skip reason the clone reports
Duplicate activityMeeting was logged earlier by hand with another subjectDelete one manually; tell the clone to skip that meeting
Wrong name or number in a noteTranscript errorFix it in the change list before approving
Scheduled run did nothingTask paused, no new meetings, or time zone mismatchAsk the clone to list its scheduled tasks and its last-run time
Proposal sent but nothing writtenWaiting for your approvalReply "approve" in chat

Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.

Paste these instructions into clone chat

# Clone Instructions: Post-Meeting CRM Autopilot (Meeting Notes → CRM Updates)

> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**

---

## 1. Role and goal

You are setting up **Post-Meeting CRM Autopilot** for your user.

When setup is done, you will run a skill called **Post-Meeting CRM Log**, on demand ("log my last meeting") and optionally on a schedule `{RUN_SCHEDULE}`, that:

1. finds the meeting and its notes (your own transcript, AI meeting notes in Drive/OneDrive or email, or notes the user pastes),
2. skips internal-only meetings and anything matching `{SKIP_RULES}`,
3. extracts the summary, decisions, next steps, deal signals, new contacts and follow-up dates,
4. matches the meeting to the CRM account, contacts and open deal,
5. checks for an existing log of the same meeting,
6. shows the user a proposed change list and waits for approval,
7. writes the approved changes to Salesforce or HubSpot,
8. optionally sends the user a short recap.

Your job right now is **setup only**: discover what is available, collect settings, propose a plan, do what you can after approval, and hand over what only the user can do. Be honest about limits. If a tool is missing or a step fails, say so and give exact manual steps.

## 2. Safety rules (read before doing anything)

1. **Plan first, then act.** Before you attach, create, schedule or change anything, show a numbered plan and wait for an explicit "yes". No yes, no changes. If the plan changes, ask again.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Connections are made by the user through the platform's sign-in (OAuth) screens. If the user pastes a secret, tell them not to and do not use it.
3. **Never email customers or prospects during setup.** The only message you may send during setup is a test recap to the user, after they approve it.
4. **No CRM writes during setup, except the approved test in section 8.** Discovery is read-only. Test writes go only to the user's test account, after approval.
5. **The running skill never writes to the CRM without an approved change list.** It never moves a deal backward, changes an amount, or closes a deal without explicit approval of that specific change.
6. **Don't guess names.** Use exact skill and operator names as they appear in the user's catalog.
7. **Each user connects their own CRM account.** Never suggest a shared service account.

## 3. Discovery

Use the `platform` tool to list your attached skills, operators and connections. Use `describeOperator` on each relevant operator to confirm what it can do and whether its connection is active.

Look for:

| Need | Required? | What to look for |
|---|---|---|
| CRM: Salesforce | One CRM required | SalesforceAccountOperator, SalesforceContactOperator, SalesforceOpportunityOperator, SalesforceActivityOperator |
| CRM: HubSpot | One CRM required | HubspotCompanyOperator, HubspotContactOperator, HubspotDealOperator, HubspotEngagementOperator |
| Notes: meeting archive | Optional | `meeting_archive` |
| Notes: Drive/Docs | Optional | GoogleDriveCoreOperator, GoogleDocsCoreOperator |
| Notes: OneDrive | Optional | Microsoft_OneDrive |
| Notes: email | Optional | GoogleGmailOperator or the Outlook email operator |
| Calendar | Optional | GoogleCalendarOperator or the Outlook calendar operator |
| Delivery | Optional | Slack or Microsoft Teams (delivery only) |
| Scheduled task | Optional (needed for automation) | `platform` scheduled tasks |

Also check whether the CRM connection has **write** access (try a harmless read, and use `describeOperator`; do not write during discovery). If you cannot tell, mark it "❓ Couldn't check".

**Report the results in a table:**

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| CRM operators | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing / ❓ Couldn't check | … | … |
| CRM write access | … | … | … |
| meeting_archive | … | … | … |
| Drive/Docs or OneDrive | … | … | … |
| Email | … | … | … |
| Calendar | … | … | … |
| Slack/Teams delivery | … | … | … |
| Scheduled task | … | … | … |

If you can't check something, mark it "❓ Couldn't check" and say why.

## 4. Collect placeholder values

Ask **once**, in a single short list. Offer examples and defaults.

> To set this up I need a few details:
>
> 1. **CRM** (`{CRM_CHOICE}`): Salesforce or HubSpot?
> 2. **Your company domains** (`{YOUR_COMPANY_DOMAINS}`): e.g. `yourcompany.com, yourcompany.io`. Meetings with only these domains are skipped.
> 3. **Where your meeting notes live** (`{NOTES_SOURCE}`, `{NOTES_FOLDER}`): my own transcripts, AI notes in a Drive/OneDrive folder (which one?), emailed notes, or pasted?
> 4. **Skip rules** (`{SKIP_RULES}`): anything else I should never log? *(default: none)*
> 5. **Schedule** (`{RUN_SCHEDULE}`): on demand only, or check for new meetings regularly (e.g. hourly, 8 AM to 6 PM, Mon-Fri, your time zone)? *(default: on demand only)*
> 6. **Delivery** (`{RECAP_DELIVERY}`): where should I send proposals and recaps: email, Slack, Teams, or chat only? *(default: chat only)*
> 7. **Auto-log mode** (`{AUTO_LOG_MODE}`): should I auto-write only the activity and summary note on scheduled runs? Deal changes, contacts and tasks always need approval. *(default: off)*
> 8. **Task defaults** (`{DEFAULT_TASK_OWNER}`, `{DEFAULT_TASK_DUE_DAYS}`): who owns a next step when no owner is stated, and the default due date. *(default: you, 3 business days)*

Repeat the answers back in a table and ask the user to confirm.

## 5. What you can do yourself (after approval)

Present a plan filled in with real names from discovery:

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing operators from the catalog: *[exact names]*.
> 2. Create the **Post-Meeting CRM Log** skill from section 7, with your values filled in.
> 3. *(If you want a schedule)* Create a scheduled task "Post-Meeting CRM Log: check for new meetings" at `{RUN_SCHEDULE}`.
> 4. Run the test in section 8 against your test account only.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.

After a clear "yes":

1. **Attach operators.** Use the `platform` tool to search the catalog and attach each approved item. Confirm each with `describeOperator`. If one needs sign-in, add it to the user's list.
2. **Create the Post-Meeting CRM Log skill.** Fill in placeholders and save it.
   - **If you can't create a custom skill directly**, give the complete skill markdown from section 7 in one copy-paste block, plus these steps:
     1. Open your clone's settings → **Skills** (or **Custom skills**).
     2. Click **New skill** / **Add skill**.
     3. Name it exactly **Post-Meeting CRM Log**.
     4. Paste the full block into the instructions field.
     5. Read it through, then **Save**.
     6. Tell me "saved" so I can verify it's attached.
     (Menu names may differ in your workspace.)
3. **Create the scheduled task** (only if the user wants one). Name: "Post-Meeting CRM Log: check for new meetings". Schedule: `{RUN_SCHEDULE}`. Action: "Run the Post-Meeting CRM Log skill in scheduled mode: find meetings that ended since the last run, prepare proposed change lists, send them to me via {RECAP_DELIVERY}, and wait for my approval before writing." If you can't create scheduled tasks, give the exact values and steps for the user to create it manually.
4. **Store the last-run marker.** Explain that the skill keeps a "last run" time (saved in your memory or a note the platform provides) and uses it to look only at newer meetings. If no storage is available, the skill falls back to "meetings that ended in the last interval".
5. **Report back** what succeeded and what failed, honestly.

## 6. What the user must do

Give this list with the how-to steps and track what is done.

1. **Connect your own CRM account (OAuth).** Open the clone's **Connections** / **Integrations** page → choose Salesforce or HubSpot → **Connect** / **Sign in** → approve the permissions. Use **your own** user, not a shared account.
   - The connection needs **WRITE** access to **contacts, companies/accounts, deals/opportunities and activities**. It does **not** need admin. If you see "permission denied", ask your CRM admin to grant edit access to those four object types (not an admin role).
   - **Some CRM connections must be finished manually.** If the connection does not complete in chat, finish it in the integrations settings, then tell me "connected" so I can re-check.
2. **Connect your notes source** (optional): Gmail or Outlook, and Google Drive/Docs or OneDrive. Same Connections page. Read access is enough (add send only if you want recap emails).
3. **Turn on AI meeting notes** in your meeting tool if you want that source, and tell me which Drive/OneDrive folder they land in (for example a "Meet Recordings" folder). Note: for meetings you did not organize, the notes may be **emailed** instead of saved to Drive.
4. **Invite me to meetings** (optional): if you want my own transcript, add my inbox to the meeting and I join with `joinMeeting`.
5. **Prepare a test account, contact and deal** in the CRM for the test run (not a real customer).
6. **Reply "approve"** to each proposed change list. On scheduled runs I will message you the list and wait.

## 7. The Post-Meeting CRM Log skill (save this in full)

Fill in the placeholders, then save as a skill named **Post-Meeting CRM Log**. Don't shorten it.

~~~~markdown
# Post-Meeting CRM Log

## Purpose
After a customer or sales meeting, turn the meeting notes into CRM updates. Find the notes, extract
what matters, match the meeting to the right account, contacts and open deal, show a proposed
change list, and write to the CRM only after the user approves.

## Settings
- CRM: {CRM_CHOICE} (Salesforce or HubSpot)
- Internal company domains: {YOUR_COMPANY_DOMAINS}
- Notes source(s): {NOTES_SOURCE}; notes folder: {NOTES_FOLDER}
- Extra skip rules: {SKIP_RULES}
- Schedule: {RUN_SCHEDULE}
- Delivery of proposals and recaps: {RECAP_DELIVERY}
- Auto-log mode: {AUTO_LOG_MODE} (off by default; when on, activity + summary note only, never deal changes)
- Default task owner: {DEFAULT_TASK_OWNER}; default task due date: {DEFAULT_TASK_DUE_DAYS}
- Activity subject format: "[Meeting Log] {Meeting title} – {YYYY-MM-DD}"
- Last-run time: stored after each scheduled run

## Tools
Use the exact names from my skill catalog. Use the CRM that matches my settings; skip what isn't connected.

| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| My own transcript of a meeting I attended | meeting_archive | Optional | Read |
| AI notes saved in Google Drive / Docs | GoogleDriveCoreOperator, GoogleDocsCoreOperator | Optional | Read |
| AI notes saved in OneDrive | Microsoft_OneDrive | Optional | Read |
| Notes emailed to the user; optional recap email | GoogleGmailOperator or Outlook email operator | Optional | Read; send ONLY a recap to the user |
| Meeting time and attendees | GoogleCalendarOperator or Outlook calendar operator | Optional | Read |
| Match account (Salesforce) | SalesforceAccountOperator | Salesforce | Read |
| Match and update contacts, create confirmed new contacts (Salesforce) | SalesforceContactOperator | Salesforce | Read; write after approval |
| Find open opportunities; apply approved changes (Salesforce) | SalesforceOpportunityOperator | Salesforce | Read; write only approved changes |
| Dedupe check, log meeting, summary, tasks (Salesforce) | SalesforceActivityOperator | Salesforce | Read; write after approval |
| Match company (HubSpot) | HubspotCompanyOperator | HubSpot | Read |
| Match and update contacts, create confirmed new contacts (HubSpot) | HubspotContactOperator | HubSpot | Read; write after approval |
| Find open deals; apply approved changes (HubSpot) | HubspotDealOperator | HubSpot | Read; write only approved changes |
| Dedupe check, meeting, note, tasks with associations (HubSpot) | HubspotEngagementOperator | HubSpot | Read; write after approval |
| Deliver proposals and recaps | Slack or Microsoft Teams (messaging integration) | Optional | Send to the user only |
| Scheduled runs | platform (scheduled task) | Optional | Existing task |

## Guardrails
- NEVER write to the CRM until the user has approved the proposed change list. Approval covers only the items approved.
- NEVER move a deal backward in stage, change a deal amount, or close a deal (won or lost) unless the user explicitly approves that specific change. Present these only as SUGGESTIONS.
- NEVER create a new contact without the user's confirmation of that contact.
- NEVER delete or overwrite existing CRM data. Add notes and tasks; update only fields the user approved. Do not overwrite a non-empty field unless the user approves.
- NEVER log a meeting twice. Before writing, search for an existing activity with the subject "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" (and a same-day activity linked to the same account with a similar title). If found, skip and say so.
- SKIP internal-only meetings (all attendees at {YOUR_COMPANY_DOMAINS}) and meetings matching {SKIP_RULES}. Report the reason.
- NEVER email or message customers, prospects or meeting attendees. The only messages you send go to the user.
- Treat transcripts and notes as unreliable for names, numbers, prices and dates. Mark uncertain values "verify" and never put an unverified amount, date or name into a deal change as a fact.
- Only record what the notes actually say. Do not invent next steps, owners, amounts or dates. If an owner or due date is missing, use the defaults and mark them "default".
- If there are several open deals at the account, ASK the user which one. Never guess.
- Scheduled runs: send the proposal to the user and wait for "approve" in chat. Write nothing until then. Only if {AUTO_LOG_MODE} is on may you auto-write the activity and summary note, and never deal changes, contact changes, new contacts or tasks.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that tool "unavailable" for this run, continue without it, and report it. If a CRM write fails twice, stop writing, report exactly what was and was not written.
- Never ask for or handle passwords or tokens. If the CRM says permission denied, tell the user the connection needs write access (not admin) to contacts, companies/accounts, deals/opportunities and activities, and that some connections must be finished in the integrations settings.

## Step 1: Pick the meeting(s) to process
- On demand: use the meeting the user names, or "my last meeting" = the most recent ended external meeting on the user's calendar. If unclear, show the 3 most recent and ask.
- Pasted notes: use the notes the user pasted; ask for the meeting title, date and attendee emails if missing.
- Scheduled run: read the stored last-run time. List meetings that ended after it (calendar, or meeting_archive entries). Process each one. When the run finishes, store the new last-run time (the time the run started). If no last-run time exists, use the last {RUN_SCHEDULE} interval.
- For each meeting capture: title, date, start/end, organizer, attendees (name + email).

## Step 2: Skip what should not be logged
- Skip if every attendee's email domain is in {YOUR_COMPANY_DOMAINS} (internal-only).
- Skip if it matches {SKIP_RULES}.
- Report each skipped meeting with its reason.

## Step 3: Find the notes
Use the first source that has notes for this meeting, in this order, and tell the user which one you used:
1. meeting_archive: a transcript from a meeting I attended that matches title/date.
2. Files: AI notes in the notes folder {NOTES_FOLDER} (GoogleDriveCoreOperator + GoogleDocsCoreOperator, or Microsoft_OneDrive), matched by title and date.
3. Email: AI meeting notes emailed to the user (GoogleGmailOperator or Outlook email operator), matched by subject and date. Notes for meetings the user did not organize often arrive here instead of Drive.
4. Pasted notes in chat.
If no notes are found, say so, tell the user where you looked, and ask them to paste notes. Do not log a meeting with no notes unless the user asks for a bare activity.

## Step 4: Extract
From the notes, extract only what is stated:
- Summary: 4-8 bullets.
- Decisions made.
- Next steps: each with owner, due date (use stated; else defaults marked "default") and who it is for (us or customer).
- Deal signals: stage hints, amount or budget mentioned, expected close date, competitors, risks and blockers, buying committee changes.
- New people mentioned (name, title, company, email/phone if stated).
- Contact facts: titles or phone numbers stated for existing attendees.
- Follow-up dates (next meeting, deadlines).
Flag anything uncertain (names, numbers, dates) with "verify".

## Step 5: Match to the CRM
1. Take external attendee email domains (not in {YOUR_COMPANY_DOMAINS}). Ignore personal domains (gmail.com, outlook.com, etc.) unless a contact with that exact email exists.
2. Account/company: Salesforce SalesforceAccountOperator, or HubSpot HubspotCompanyOperator, matched by domain/website. If none or several match, ask the user.
3. Contacts: match each attendee by email (SalesforceContactOperator / HubspotContactOperator). List attendees with no contact record as possible new contacts.
4. Open deal: SalesforceOpportunityOperator (not closed) / HubspotDealOperator (not Closed Won/Lost) for the account. One open deal: use it. Several: list them (name, stage, amount, close date) and ASK which one, or "none". No open deal: do not create one; note it.

## Step 6: Dedupe
Search for an existing activity with subject "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" (SalesforceActivityOperator, or HubspotEngagementOperator) on the matched account/company/contact. If found, skip logging, tell the user, and stop for this meeting.

## Step 7: Build and show the proposed change list
Show a numbered list. Mark each item as WRITE (needs approval), NEW CONTACT (needs confirmation) or SUGGESTION (deal change; needs explicit approval). Include the notes source used, the matched account, contacts and deal, and any "verify" flags.

1. Log meeting: subject "[Meeting Log] {Meeting title} – {YYYY-MM-DD}", date, attendees, linked to account, contact(s) and deal.
   - Salesforce: SalesforceActivityOperator task/event with WhoId = contact, WhatId = account or opportunity.
   - HubSpot: HubspotEngagementOperator meeting associated to contact(s), company and deal.
2. Summary note: the summary, decisions and deal signals, linked the same way (HubSpot: a note engagement; Salesforce: in the activity description or a note-type activity).
3. Follow-up tasks: title, owner, due date, linked to account/contact/deal.
4. Contact updates: only stated titles or phone numbers, showing old and new values.
5. New contacts: name, title, email, account. Each needs the user's confirmation.
6. SUGGESTED deal changes: stage, amount, close date, with the reason (quote from the notes) and the current value. Mark backward moves, amount changes and closings as "needs explicit approval".
End with: "Reply approve (all), approve 1-3 (some), or tell me what to change."

## Step 8: Wait for approval
- Write only what the user approved. For SUGGESTIONS, only the specific changes the user explicitly approved.
- Scheduled runs: deliver the list to the user via {RECAP_DELIVERY} and wait for "approve" in chat. Do not write while waiting.
- Auto-log mode (only if {AUTO_LOG_MODE} is on, scheduled runs only): after the dedupe check, write the activity and summary note, then send the rest of the list for approval.

## Step 9: Write
Perform the approved writes in this order: meeting/activity, summary note, tasks, contact updates, confirmed new contacts, approved deal changes. After each write, read it back (or use the returned ID) to confirm. If a write fails, retry ONCE, then stop and report.

## Step 10: Confirm and recap
- Reply with what was written (with links or IDs where available), what was skipped, and what is waiting.
- If recap delivery is set, send the user a short recap (3-6 lines) by {RECAP_DELIVERY}. Never send to anyone else.
- On scheduled runs, update the stored last-run time.

## Output format
**Post-Meeting CRM Log: {Meeting title} ({YYYY-MM-DD})**
- Notes source: …
- Matched: account …, contacts …, deal …
- Skipped / duplicate check: …
- Proposed changes: numbered list as in Step 7
- Verify flags: …
- Status after approval: written ✅ / skipped ⏭️ / failed ❌ per item
- Source status: each tool worked / no data / unavailable
~~~~

## 8. Test plan

Ask the user to approve the test first. Use a **test account, test contact and test deal** (never a real customer).

1. The user creates the test records (or points you to them) and makes a short test note, for example: "Met with {Test Contact} from the test account. Decided to run a pilot. We will send a proposal by Friday (me). They will share a security questionnaire next week. {Test Contact} is now Head of Operations. Possible new stakeholder: Pat from Procurement. Close date likely moves to next month."
2. Run the skill on the pasted note: "Log this meeting."
3. Review the proposed change list together. Approve all, including one suggested deal change.
4. Run it **again** on the same meeting to test dedupe.
5. Verify in the CRM (user checks).

| Check | Pass? |
|---|---|
| Internal-only meeting (if tested) was skipped with the reason | ☐ |
| Meeting matched the test account, contact and deal | ☐ |
| Change list appeared and **nothing was written before approval** | ☐ |
| Activity/meeting logged with subject "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" and linked to account, contact and deal | ☐ |
| Summary note present and accurate | ☐ |
| Follow-up tasks have correct owners and due dates | ☐ |
| Contact title updated (old and new shown in the list) | ☐ |
| New contact was created **only after confirmation** | ☐ |
| Deal stage/amount/close date changed only where explicitly approved; no backward move or close | ☐ |
| Second run was skipped as a duplicate | ☐ |
| (If several test deals exist) clone asked which deal to use | ☐ |
| (If scheduled) proposal was delivered and clone waited for "approve" | ☐ |
| No email or message was sent to the test contact | ☐ |

6. Fix anything that failed and re-run. Then the user deletes the test records and test activities.

## 9. Final status checklist

When you finish, send the user a status summary in this format:

**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] CRM operators attached: …
- [ ] Notes-source operators attached: …
- [ ] Post-Meeting CRM Log skill created (or full text handed over for copy-paste)
- [ ] Scheduled task created for `{RUN_SCHEDULE}` (if wanted)
- [ ] Test run completed; results: …

**⏳ Waiting on you**
- [ ] Connect your own CRM account with write access (admin not needed); finish in integrations settings if chat can't complete it
- [ ] Connect Gmail/Drive or Outlook/OneDrive (if using AI notes)
- [ ] Turn on AI meeting notes and tell me the folder
- [ ] Save the skill (if I handed it over)
- [ ] Approve change lists by replying "approve"
- [ ] Delete test records

**💡 Optional next steps**
- [ ] Turn on a schedule (`{RUN_SCHEDULE}`) and Slack/Teams delivery
- [ ] Try auto-log mode (`{AUTO_LOG_MODE}`) for activity + note only
- [ ] Add `{SKIP_RULES}` after the first week
- [ ] Invite me to meetings so I can use my own transcript (`joinMeeting`)
- [ ] Adjust the note template or task defaults

Requirements

Requirements: Post-Meeting CRM Autopilot

Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 30–60 minutes

Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.


1. Required skills / operators

Use the exact names below. Confirm them in your skill catalog before saving the skill. Your clone will report the exact names it finds.

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

Pick one CRM (required):

#Skill / operator (exact name)What it's used forNotes
1SalesforceAccountOperatorMatch attendee domain to an accountSalesforce users
2SalesforceContactOperatorMatch attendees; update title/phone; create confirmed new contactsSalesforce users
3SalesforceOpportunityOperatorFind open opportunities; apply approved stage, amount, close date changesSalesforce users
4SalesforceActivityOperatorCheck for duplicates; log the meeting; add the summary; create follow-up tasksSalesforce users
5HubspotCompanyOperatorMatch attendee domain to a companyHubSpot users
6HubspotContactOperatorMatch attendees; update title/phone; create confirmed new contactsHubSpot users
7HubspotDealOperatorFind open deals; apply approved stage, amount, close date changesHubSpot users
8HubspotEngagementOperatorCheck for duplicates; log the meeting; add the note; create tasks, with associationsHubSpot users

Also required:

#Skill / operator (exact name)What it's used forNotes
9Post-Meeting CRM Log (custom skill)The workflow itselfSaved from CLONE-INSTRUCTIONS.md section 7
10Scheduled task (via the platform tool)Check for new meetings on {RUN_SCHEDULE}Only if you want automation; not needed for on-demand use
11At least one notes source (see below)Find the meeting contentPasted notes always work

Notes sources (use any that apply):

SourceExact nameNotes
Clone's own transcriptsmeeting_archiveOnly meetings the clone attended
AI notes in Google Drive / DocsGoogleDriveCoreOperator, GoogleDocsCoreOperatorFor example Gemini notes in a "Meet Recordings" folder
AI notes in OneDriveMicrosoft_OneDriveMicrosoft 365 users
Emailed notesGoogleGmailOperator or the Outlook email operatorCommon for meetings you did not organize
Calendar (optional)GoogleCalendarOperator or the Outlook calendar operatorAttendees and meeting times
Pasted notesNone neededPaste into chat

2. Connections and minimum permissions

ConnectionMinimum permissionWhy
Salesforce or HubSpotWRITE access to contacts, companies/accounts, deals/opportunities and activities (HubSpot: contacts, companies, deals, engagements/notes/tasks). Admin is NOT required.Match records, log the meeting, create tasks, update contacts, apply approved deal changes
Gmail or Outlook (optional)Read (add Send only if you want recap emails)Find emailed AI notes; send the optional recap to you
Google Drive / Docs or OneDrive (optional)View the notes folderRead AI meeting notes
Google Calendar or Outlook calendar (optional)ReadAttendees and times
Slack or Teams (optional)Post to youDeliver proposals and recaps

Important points:

  • Each user connects their own CRM account. No shared service accounts, so activities are attributed correctly and the clone only sees what you can see.
  • Write access is not admin. A common mix-up: you do not need a CRM administrator account. You need a normal user whose profile or permission set allows editing the four object types above.
  • Some CRM connections must be finished manually in the clone's Connections / Integrations settings instead of in chat.
  • All connections are made by you through the platform's sign-in (OAuth). Your clone never needs your password.

3. Optional add-ons

Add-onAddsOperators
meeting_archiveClone's own transcript for meetings it attended (join with joinMeeting)meeting_archive, joinMeeting
CalendarReliable attendee lists and times for matchingGoogleCalendarOperator or Outlook calendar operator
Slack or TeamsProposal and recap delivery in your messaging appClone's messaging integration
Recap emailShort email to you listing what was loggedGoogleGmailOperator or Outlook email operator
Auto-log modeWrites activity + summary note without waiting (never deal changes){AUTO_LOG_MODE} setting

Salesforce ⇄ HubSpot mapping

Generic conceptSalesforceHubSpot
Account / companyAccount (SalesforceAccountOperator)Company (HubspotCompanyOperator)
ContactContact (SalesforceContactOperator)Contact (HubspotContactOperator)
Opportunity / dealOpportunity (SalesforceOpportunityOperator)Deal (HubspotDealOperator)
Logged meetingEvent (or completed Task) via SalesforceActivityOperatorEngagement of type Meeting via HubspotEngagementOperator
Summary noteTask or Event description (or a Note-type activity) via SalesforceActivityOperatorEngagement of type Note via HubspotEngagementOperator
Follow-up taskTask via SalesforceActivityOperator (Subject, ActivityDate, Owner)Engagement of type Task via HubspotEngagementOperator (title, due date, owner)
AssociationsWhoId (contact) and WhatId (account or opportunity) on the activityMeeting and note associated to contact, company and deal
StageOpportunity Stage (StageName)Deal stage (dealstage) in the deal's pipeline
AmountOpportunity AmountDeal amount
Close dateOpportunity CloseDateDeal closedate
Open vs closedIsClosed = falseDeal stage is not Closed Won or Closed Lost
OwnerOwner (User)Contact / deal owner

Field names and stage labels vary by setup. The clone reads your actual stage names and pipeline from the CRM before suggesting anything.

Google ⇄ Microsoft 365 mapping

ConceptGoogle WorkspaceMicrosoft 365
EmailGmail (GoogleGmailOperator)Outlook email operator
CalendarGoogle Calendar (GoogleCalendarOperator)Outlook calendar operator
Files with AI notesGoogle Drive (GoogleDriveCoreOperator) + Docs (GoogleDocsCoreOperator), e.g. Gemini notes in "Meet Recordings"OneDrive (Microsoft_OneDrive)

4. Data prerequisites

  • Accounts have domains. CRM accounts/companies have a website or email domain, and contacts have email addresses, so matching works.
  • You know your open deals. Open opportunities/deals exist for the accounts you meet, and stages are in use.
  • {YOUR_COMPANY_DOMAINS} listed, so internal meetings are skipped.
  • A notes source is available: AI meeting notes turned on in your meeting tool, or the clone attends meetings, or you are willing to paste notes.
  • A test account, contact and deal exist for the test run (not a real customer).
  • Your CRM user can edit contacts, accounts/companies, deals/opportunities and activities.

5. Roles and permissions

WhoNeeds to
Clone admin (owner of the clone)Attach operators, approve the plan, save the Post-Meeting CRM Log skill, create or approve the scheduled task
CRM user (each person)Connect their own Salesforce or HubSpot account with write access (admin not needed); approve change lists
CRM admin (only if your org restricts permissions)Grant the user write access to contacts, accounts/companies, deals/opportunities and activities
Notes ownerMake sure AI notes are saved somewhere the clone can read, or share the folder
RevOps (optional)Review stage definitions, required fields and activity subject conventions

6. Estimated setup time

StepTime
Pre-flight check (this doc)5 min
Clone discovery + placeholders + plan10 min
Your CRM and notes-source connections10–20 min
Save skill + optional scheduled task5–10 min
Test run10–15 min
Total30–60 min

7. Pre-flight checklist

  • I'm the clone admin (or have one available)
  • I use Salesforce or HubSpot and can sign in with my own account
  • My CRM user has write access to contacts, accounts/companies, deals/opportunities and activities (admin not needed)
  • I know where my meeting notes come from (meeting_archive, Drive/OneDrive, email, or pasted)
  • I know my {YOUR_COMPANY_DOMAINS}
  • I've decided on {SKIP_RULES} (or none)
  • I've decided whether to schedule it ({RUN_SCHEDULE}) and how I get proposals ({RECAP_DELIVERY})
  • I've decided {AUTO_LOG_MODE} (default: off)
  • I have a test account, contact and deal in the CRM
  • I can create scheduled tasks (or the clone can)

8. You're ready when…

  • ✅ The operators for your CRM are attached and the connection is signed in with write access.
  • ✅ At least one notes source works (or you are ready to paste notes).
  • ✅ You have answers for the placeholders in README section 6.
  • ✅ You have a test account, contact and deal.
  • ✅ You are comfortable replying "approve" to a change list.

Then download CLONE-INSTRUCTIONS.md and give it to your clone.

Was this use case helpful?