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

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

Airtable + Apollo + lemlist

IntermediateSDRsMarketing

Who it's for

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.

What you get

Tiered attendee table and drafts, waiting for approval. Sample output: every company and person in it is 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.

Time and cost

Estimate About 30–45 minutes the day after the event, most of it checking tiers and writing Tier 1 notes.

Assumptions: One event with about 60 badge scans, about 55 left after cleanup, two lemlist campaigns for Tiers 2 and 3, and Tier 1 sent by hand.

Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.

MCP servers

Every server is confirmed in: ClaudeChatGPTClaude CodeCursor

Set up in a chat app

Every server in this recipe is confirmed for Claude and ChatGPT. Connect each one, then paste the prompts below into one conversation.

Developer setup

Auth setup and mcp.json for Claude Code and Cursor
  • Airtable: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.
  • Apollo: Use OAuth sign-in for interactive use. For headless runs, use an API key in the X-Api-Key header.
  • lemlist: Use OAuth sign-in for interactive use. For headless runs, use an API key in the X-Api-Key header.

Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.

{
  "mcpServers": {
    "airtable": {
      "url": "https://mcp.airtable.com/mcp"
    },
    "apollo": {
      "url": "https://mcp.apollo.io/mcp"
      // headless alternative: "headers": { "X-Api-Key": "YOUR_APOLLO_API_KEY" }
    },
    "lemlist": {
      "url": "https://app.lemlist.com/mcp"
    }
  }
}

Step-by-step prompts

  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.

Run it on a schedule (optional)

Where this goes wrong

Gotchas

Download

Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.

Download event-follow-up-24h.md

Vendor sites: Apollo. If we join an affiliate program, these links will be labeled as affiliate links.