meeting-to-opportunity

Meeting to Opportunity

Pulls recent NoteTaker meetings, matches each to a CRM deal, and writes structured notes back as monday updates. Reverse-Salesforce-Einstein — Salesforce ships this loop, monday hasn't (until now). Cross-product stickiness for NoteTaker + CRM users.

Flow: Trigger → Pull meetings → Match → Synthesize → Publish (α) → Auto-contact (β, opt-in) → Proactive next-step nudges (opt-in).

Input

• Optional: time window via argument (default = last 24h).
• Optional: pre-declared mode (Default / Silent / Proactive).

Output

• α (default): One Meeting recap update per matched deal, summarizing key points + commitments + next steps. Body carries the Generated by Claude · <ISO timestamp> footer + <!-- claude-skill-id: meeting-to-opportunity --><!-- meeting-id: <id> --> comments. A Meeting sync — <Mon DD> doc lists what was matched, what wasn't, and unresolved attendees.
• β (Auto-contact, opt-in): New items on the Contacts board for meeting attendees not already in CRM, linked back to the matched deal. Each new contact carries Source = Claude on a status column.
• Proactive extension: create_notification to deal owner for commitments due this week. Stage column edits and last-touch updates are also OK in Proactive (or in Default with batched confirm) when a clear transition phrase is present in the transcript ("we agreed to move to procurement review", "they signed today"). Surfaced as a single batched plan: " stage transitions detected. Apply all / review each / skip stage edits?". Amount-column writes still forbidden.

Knowledge

• Meeting → deal matching heuristic (§ Step 4).
• Update body convention (§ Step 6).
• Shared artifact conventions (§ Shared patterns).

Tools (MCP)

• get_user_context — user identity for filtering meetings.
• get_notetaker_meetings — recent meetings + transcripts.
• search / list_workspaces / get_board_info — locate Deals + Contacts boards.
• get_board_items_page — fetch active deals to match against.
• get_column_type_info — resolve email/company columns by type.
• create_update — write the recap onto the matched deal.
• create_item — β auto-contact on the Contacts board.
• change_item_column_values — populate the new contact's email + company columns, write Source = Claude on contacts, and apply confirmed stage / last-touch edits on matched deals. Never for amount columns.
• create_notification — proactive next-step nudges.
• create_doc — sync summary doc.
• all_monday_api — escape hatch for connect-board column writes (linking contact ↔ deal).

Cross-skill handoffs

• From workspace-builder / morning-briefing: suggested as a way to keep deals fresh after a meeting-heavy day.
• To bulk-data-hygiene: if >30% of attendees couldn't be matched, suggest running bulk-data-hygiene to clean contact data.
• To morning-briefing: the synced updates feed tomorrow's brief.

Step 0: Connector check + NoteTaker availability

Goal: Fail fast if either the monday MCP connector or NoteTaker is missing.

1. Try mcp__monday__get_user_context. On error → standard install prompt, stop.
2. Try mcp__monday__get_notetaker_meetings({ limit: 1 }).
3. If NoteTaker tool returns auth error or empty-by-permission:
   • Print: "NoteTaker isn't connected for this account, or you don't have meetings recorded yet. Set up NoteTaker at , then re-run."
   • Stop.

PAUSE: do not write any create_* call before Step 6.

Step 1: Detect mode

• Default — bundle all writes (recaps + stage edits + last-touch updates + auto-contacts) into a single batched confirm before executing.
• Silent — skip the batched confirm; β auto-contact still requires explicit opt-in.
• Proactive — ask once: "Proactive mode will: (a) write recaps to matched deals, (b) auto-create missing contacts, (c) apply stage/last-touch edits when transcripts are unambiguous, (d) notify deal owners on commitments due this week. Amount columns stay untouched. Approve all / review each batch / deny stage edits only?". Cache the choice.

If undeclared, Default.

Hard safety rail regardless of mode: no deletes, no amount-column writes, no cross-workspace moves. Stage transitions are bundled into a batched plan — never written one-off, never silently.

Step 2: Resolve time window

1. If argument carries a phrase, parse: "today" / "yesterday" / "last N days" / "since YYYY-MM-DD".
2. Default = last 24h.
3. If parsed window > 14 days: confirm via AskUserQuestion (large windows produce noisy recaps).

Step 3: Pull meetings

mcp__monday__get_notetaker_meetings({ since: <ISO>, until: <ISO>, limit: 50 }). Cache transcripts + attendees + meeting metadata.

Edge cases:

• 0 meetings in window: print "No NoteTaker meetings found in <window>. Try a wider range, e.g. last 7 days." Stop.
• >50 meetings: paginate up to 200, then cap and surface sampling note.
• Tool 429: backoff 3x; on third failure stop with "NoteTaker is rate-limiting; retry in 60s."

Step 4: Resolve Deals + Contacts boards (Gather)

Resolve the boards directly — this skill is self-contained:

1. Deals board: get_user_context → scan favorites + relevantBoards for names matching deals|opportunities|pipeline|sales. One candidate → use it; multiple → AskUserQuestion; zero → list_workspaces → search("deal", BOARD). Still zero → degrade per step 4 below.
2. Contacts board: same pass for contacts|people|leads (only if β auto-contact may run).
3. get_board_info on each. Resolve columns by type:
   • On Deals: email (if present), text company-name, people owner, status stage, numbers value, date last-touch.
   • On Contacts: email, text (or company-link board_relation), phone, people owner.
4. If Deals board missing entirely: degrade — skip α, write only the sync summary doc with "no Deals board found" header. Suggest /monday-crm:workspace-builder.

Step 5: Match meetings → deals (Synthesize)

Goal: For each meeting, find the single best matching deal — or flag it as unmatched.

For each meeting:

1. Extract signals: attendee emails (excluding internal monday domain), company names from email domains, meeting title keywords.
2. Pull active deals (Pass A from morning-briefing — non-Won/Lost), limit: 500.
3. Score candidates:
   • +5 per attendee email matching a deal's email column.
   • +3 per attendee email domain matching a deal's company-name column (case-insensitive substring).
   • +2 if meeting title contains a deal name (≥3 contiguous chars match).
   • +1 if meeting attendee is the deal's owner (intra-team meetings without external attendees → likely internal review of that deal).
4. Pick the top score if it's ≥5 AND beats the second-best by ≥3. Otherwise flag as ambiguous (multiple candidates) or unmatched (no candidate ≥5).
5. Multi-deal meetings: if top two candidates are within 2 points and both ≥5, flag as multi-match — write the recap to both deals with a header line "Meeting also discussed: ".

Edge cases:

• Internal-only meetings (all attendees @monday.com or @<company-domain>) and no deal-name title match: skip (likely standup), log to summary doc as "skipped: internal-only".
• Personal-meetings filter: skip meetings tagged 1:1 (no transcript content of CRM relevance).

Step 6: Synthesize the recap (Synthesize)

For each matched meeting, compose a structured recap from the transcript:

• Key points (3–5 bullets, factual — what was discussed).
• Commitments made (who → what → by when, parsed from "I'll send you...", "we'll follow up by...", "next week we...").
• Open questions (statements ending with ? or signaled by "we need to figure out", "TBD").
• Stage transition signal: if transcript contains procurement / legal / contract / close phrases, propose a stage change. Mark each as confidence: high|low based on (a) explicit phrase ("we agreed to ", "signed today") = high, (b) inferred ("seems like they're ready for legal review") = low. Only high transitions enter the batched plan; low ones surface as text recommendations.

Deal-side metadata lookup: pull current stage + value + close date for context (single get_board_items_page filtered to the matched item ID).

Step 7: Publish α — per-deal recap (Publish)

For each matched meeting + deal pair:

1. Idempotency: search recent updates on the deal item for one carrying both <!-- claude-skill-id: meeting-to-opportunity --> and <!-- meeting-id: <id> -->. If found → update via all_monday_api, don't post a duplicate.
2. create_update({ itemId: <dealId>, body: <recap markdown> }).
3. Update body shape:

# Meeting recap — <meeting title>
*<meeting date> · <duration>m · <attendee count> attendees*

## Key points
- ...

## Commitments
- <person> → <commitment> (due <date or "open">)

## Open questions
- ...

## Stage signal
<"applied: <old> → <new>" if the batched plan included it> OR <text recommendation if low-confidence> OR "no stage change">

---
<!-- claude-skill-id: meeting-to-opportunity -->
<!-- meeting-id: <noteTakerMeetingId> -->
Generated by Claude · <ISO timestamp> · run `/monday-crm:meeting-to-opportunity` to refresh.

Batched confirm (Default mode)

Before any write, print a single plan: "I'll write: recaps · stage edits (high-confidence only) · last-touch updates · new contacts. meetings unmatched (will list separately). low-confidence stage signals will surface as text only. Proceed? (yes / show plan in detail / no)."

# Meeting sync — <Mon DD>

## Matched (<N>)
- <meeting title> → <deal name> (<deal url>)

## Multi-match (<N>)
- <meeting title> → <deal A> + <deal B>

## Ambiguous (<N>)
- <meeting title> — candidates: <deal A>, <deal B> — review and re-run with explicit deal ID

## Unmatched (<N>)
- <meeting title> — attendees: <emails> — no matching deal. Suggest creating one.

## Skipped (<N>)
- <meeting title> — internal-only, no CRM relevance

## Contacts created (<N>)
- <name> (<email>) → linked to <deal>

---
Generated by Claude · <ISO timestamp>