wdm0006 Event Follow-Up Workflow
Works with Evergreen, a local-first personal CRM for macOS. Get it on the Mac App Store.
When to Use
- After a conference, meetup, dinner, or networking event
- You have a stack of business cards or a list of people you met
- You want to batch-create contacts and send personalized follow-ups
- After hosting or attending a group event
How It Works
- Parse the attendee list or notes to extract contact details
- For each person, check for duplicates with
search_contacts - Create new contacts with
create_contact - Tag all contacts with the event name via the
tagsfield onupdate_contact - Log the initial meeting as an interaction with
log_interaction - Add conversation context to the contact's
noteswithupdate_contact(include who introduced you when the notes name an introducer) - If the notes say a specific person introduced you to this contact, resolve that introducer with
search_contacts. If they're already in the CRM, callrecord_introduction(introducerId, newContactId, notes?)to record theintroducedByedge. If the introducer isn't a known contact, skip the call and keep the note from step 6. - Draft personalized follow-up messages for each contact
- Create follow-up actions with
create_action
Event Tag Convention
Use consistent event tags for easy filtering later:
Format: event-[name]-[year]
Examples:
event-ai-dinner-2026
event-pycon-2026
event-founders-retreat-q1
event-team-offsite-apr26
Example
Input: Notes from Atlanta AI Dinner
Met at Atlanta AI Dinner, April 3, 2026:
1. Sarah Chen — CTO at Meridian Health. Talked about healthcare data
pipelines. Very interested in our API. sarah@meridianhealth.com
2. Marcus Webb — Founder of DataFlow. Building real-time analytics.
Previously at Google. marcus@dataflow.io
3. Priya Sharma — ML Engineer at NewCo. Working on NLP for
customer support. priya@newco.ai. Introduced by David Kim.
Batch processing:
For each contact:
1. search_contacts({ query: "[name]" }) → check for duplicates
2. create_contact({ ... })
3. update_contact({ contactId: id, tags: ["event-ai-dinner-2026", "atlanta", "ai"] })
4. log_interaction({
contactId: id,
type: "meeting",
description: "Met at Atlanta AI Dinner — [conversation topic]"
})
5. update_contact({ contactId: id, notes: "[conversation details]" })
6. create_action({
contactId: id,
title: "Send follow-up email to [name]",
dueDate: "2026-04-05",
priority: "medium"
})
For Priya Sharma, the notes say "Introduced by David Kim" — record that edge:
7. search_contacts({ query: "David Kim" }) → matches contact david_id
8. record_introduction({ introducerId: david_id, newContactId: priya_id, notes: "Introduced Priya at the Atlanta AI Dinner" })
(If David Kim isn't already a contact, skip this and keep "Introduced by David Kim" in Priya's notes.)
Sample follow-up for Sarah:
Subject: Great meeting you at the AI Dinner
Hi Sarah,
Really enjoyed our conversation about healthcare data pipelines last
night. The challenges you described with real-time patient data are
exactly the kind of problems I find fascinating.
I'd love to continue the conversation — especially around how our
API might fit into Meridian's architecture. Free for a quick call
next week?
Best,
[Name]
Follow-Up Timing
| Priority | When to Send | Who |
|---|---|---|
| Same night / next morning | People you had deep conversations with | |
| Within 48 hours | Everyone else you want to stay in touch with | |
| Within a week | Lower priority but still worth connecting | |
| Skip | Brief hellos with no real connection point |
Checklist
Event Follow-Up:
- [ ] All contacts created with complete details
- [ ] Event tag applied consistently
- [ ] Initial interaction logged with conversation context
- [ ] Notes capture what you discussed (not just who they are)
- [ ] Introducer edge recorded with `record_introduction` for anyone the notes say was introduced by a known contact
- [ ] Follow-up messages personalized per conversation
- [ ] Follow-up actions created with appropriate deadlines