# Event follow-up within 24 hours: enrich the attendee list, tier it and load tiered follow-ups

Source: https://mcpforgtm.com/recipes/event-follow-up-24h (StackMCP, independent directory of official MCP servers)

## Goal

SDRs and event marketers who come back from a conference or field event with a list of badge scans and want every attendee followed up the next day, with the best ones getting a personal note. Airtable can be swapped for Typeform if your sign-ups live in a form, Apollo for Lusha, Cognism or ZoomInfo, and lemlist for Smartlead or Instantly.

## Connected tools

- Airtable: https://mcp.airtable.com/mcp (setup: https://mcpforgtm.com/tools/airtable)
- Apollo: https://mcp.apollo.io/mcp (setup: https://mcpforgtm.com/tools/apollo)
- lemlist: https://app.lemlist.com/mcp (setup: https://mcpforgtm.com/tools/lemlist)

## Guardrails

- Read only in Airtable. Don't create, update or delete records.
- Clean the list and tell me the count before any Apollo enrichment, and enrich only after I approve it.
- Show me the tier table and every draft before anything goes into lemlist.
- Add leads to lemlist campaigns only after I approve it. Never start, resume or send a campaign, and don't send any message.
- Skip anyone already in another lemlist campaign or on my exclusion list.

## Steps

1. Find my Airtable base {base name} and the table {attendee table}. List the attendees from {event} with name, email, company, title and {notes field}. Flag duplicate emails, rows with no email, and anyone from {our domain}. Don't change anything in Airtable.
2. Tell me how many attendees are left after cleanup and wait for my OK. Only after I approve it, enrich them with Apollo people enrichment, at most {max} people. Show me title and company from Apollo next to the Airtable values, and mark blanks and conflicts.
3. Sort them into tiers with these rules: {tier rules, e.g. Tier 1: ICP company and a booth conversation; Tier 2: ICP company, scan only; Tier 3: everyone else}. Search lemlist leads for each email and flag anyone already in a campaign or on {exclusion list}. Show me a table with each person, their tier and the reason.
4. Draft the follow-ups: a personal note for each Tier 1 person that uses their {notes field}, and one short template each for Tier 2 and Tier 3 that mentions {event}. Show me the text only. Don't send anything.
5. Show me the status of my lemlist campaigns {tier 2 campaign} and {tier 3 campaign}. If either is running, stop and tell me. Otherwise, only after I approve it, add the approved Tier 2 and Tier 3 people as leads to the matching campaign. Don't start any campaign or send anything.

## Expected output

Tiered attendee table and drafts, waiting for approval. Example (all names fictional):

```
Event: Northbank RevOps Summit (fictional), booth, Oct 15
Source: Airtable base 'Events 2026', table 'Booth scans', 64 rows
Removed before enrichment: 5 duplicate emails, 3 rows with no email, 2 of our own team.
Enriched in Apollo: 54 people (credits used, as shown in Apollo).

| Tier | Count | Rule |
|---|---|---|
| 1 | 6 | ICP company and a booth conversation in the notes |
| 2 | 21 | ICP company, badge scan only |
| 3 | 27 | Outside ICP or title not a buyer |

Tier 1 (personal notes, you send these yourself):
| Name | Company | Title | Booth note |
|---|---|---|---|
| Dana Okafor | Fernhill Software (fictional) | VP Revenue Operations | Asked how forecast rollups work across regions |
| Sam Whitlock | Quarry Lane Analytics (fictional) | Head of Sales Ops | Wants to see it with three managers |
...4 more

Flagged: Alex Rivera, Mossgate Labs (fictional), is already a lead in lemlist campaign 'Q4 outbound'. Not added anywhere.
Conflict: Priya Raman's row says Larkspur Freightworks (fictional), Apollo returned a different employer. Held for review.

Draft, Tier 1, Dana (text only):
Subject: Forecast rollups across regions

Hi Dana,

Good to meet you at the booth yesterday. You asked how rollups work when each region forecasts differently. I've put together a short walkthrough of that exact case. Want me to send it, or go through it live on Thursday?

Jordan

Tier 2 template: 'Thanks for stopping by at Northbank' plus one line on {pain point} and a link to the recording.
Tier 3 template: a short thank-you with the slides. No meeting ask.

lemlist: 'Northbank Tier 2' is paused, 'Northbank Tier 3' is a draft. No leads added yet and no campaign started. Reply 'approve tier 2' and 'approve tier 3' to add them.
```

## Watch for

- Leads added to a campaign that is already running: If the campaign is live, new leads may start getting its steps before you've checked the copy. Read each campaign's status first, add leads only to a paused or draft campaign, and start it yourself in lemlist.
- Credits spent on junk rows: Badge scans include duplicates, blank emails, staff and vendors. Remove duplicates by email, drop rows with no email and your own domain, and confirm the final count before Apollo enrichment runs.
- The wrong tier from mismatched data: The scan may show an old employer while Apollo shows a new one, which changes the tier. Show both companies side by side and hold any conflict for review instead of tiering it.
- A customer or someone in another campaign gets a cold follow-up: Search lemlist leads for each email and give it {customer and open-deal list} to exclude. List matches separately and don't add them to any campaign.