| name | processing-meeting-notes-for-evergreen |
| description | Processes raw meeting notes into structured Evergreen CRM records — logs interactions, creates action items, adds new contacts, and updates notes. Use after any meeting, call, or conversation to capture everything in your CRM without manual data entry. |
Post-Meeting Notes Processor
Works with Evergreen, a local-first personal CRM for macOS. Get it on the Mac App Store.
When to Use
- After a meeting, call, or coffee chat
- When you have voice-transcribed notes to process
- After a group meeting with multiple contacts
- When you jotted down quick notes and want to formalize them
How It Works
- Parse the raw notes to identify: attendees, topics discussed, decisions made, action items, and new contacts mentioned
- Match attendees to existing contacts with
search_contacts
- Log the interaction for each attendee with
log_interaction
- Create action items with
create_action for any commitments
- For new people mentioned, create contacts with
create_contact
- Append detailed notes to the contact's
notes field with update_contact for relevant contacts
- Create relationships with
create_relationship if new connections were established
Extraction Targets
| Element | What to Look For | Evergreen Action |
|---|
| Attendees | Names, titles, companies | Match or create contacts |
| Topics | Key subjects discussed | Include in interaction summary |
| Decisions | Agreed-upon outcomes | Note in interaction + notes |
| Action items | "I'll...", "You should...", "Let's..." | create_action with due dates |
| New contacts | "You should talk to..." | create_contact + flag for follow-up |
| Relationships | "Sarah works with Marcus on..." | create_relationship |
| Follow-ups | Next meeting, deadlines | create_action with dates |
Example
Raw meeting notes:
Call with Sarah Chen and Lisa Park from Meridian Health on Apr 5.
Discussed the API integration timeline. Sarah wants to start the
pilot in Q3. Lisa is handling the procurement side — she needs our
security questionnaire filled out by end of April.
They mentioned their new data engineer Raj Patel would be our main
technical contact. Sarah will send his details.
We agreed to:
- Send the security questionnaire by Apr 15
- Schedule a technical deep-dive with Raj once connected
- Sarah will share their data schema doc by next week
Processed into Evergreen:
1. log_interaction({
contactId: sarah_id,
type: "call",
description: "Discussed API integration — Q3 pilot start. Lisa handling procurement. New tech contact Raj Patel joining."
})
2. log_interaction({
contactId: lisa_id,
type: "call",
description: "Procurement discussion for API integration. Needs security questionnaire by end of April."
})
3. create_action({
contactId: lisa_id,
title: "Send security questionnaire to Lisa Park",
dueDate: "2026-04-15",
priority: "high"
})
4. create_action({
contactId: sarah_id,
title: "Schedule technical deep-dive with Raj Patel (after intro)",
priority: "medium"
})
5. create_action({
contactId: sarah_id,
title: "Follow up if Sarah hasn't sent data schema doc by Apr 12",
dueDate: "2026-04-12",
priority: "medium"
})
6. update_contact({ contactId: sarah_id, notes: "Apr 5 call: Q3 pilot confirmed. New tech contact: Raj Patel (data engineer). Lisa handling procurement." })
Checklist
Post-Meeting Processing:
- [ ] All attendees identified and matched to contacts
- [ ] Interaction logged for each attendee
- [ ] All action items captured with owners and due dates
- [ ] New contacts created (or flagged for creation)
- [ ] Relevant notes appended to contact records
- [ ] Relationships updated if new connections established
Learn More
