n8n Event Lead Follow-Up: From Badge Scan to Booked Call

A sales team comes back from a three-day conference with 400 badge scans and follows up with maybe 40 of them, a week later, when the leads have gone cold. That's the normal outcome, and it's a waste of a five-figure booth. n8n event lead follow-up fixes the part that actually loses deals: the lag between the conversation and the first email.

Event leads decay faster than almost any other source. The prospect remembered your pitch on Tuesday afternoon. By the following Monday they've talked to nine other vendors and can't tell you apart. Speed-to-lead is the entire advantage of being at the event in the first place, and a manual upload-then-mail-merge process throws it away.

This shows how to ingest a badge scan, score the conversation with AI, and fire a personalized follow-up to the hot leads automatically, while the warm ones drop into a queue for a rep.

What you can automate

• Ingest a badge scan or booth form the instant it's captured
• Score each lead 1–10 on title, company seniority, and conversation notes
• Auto-send a personalized follow-up to hot leads within seconds
• Alert a rep on Slack the moment a high-value lead is identified
• Dedupe so the same contact never gets two emails from one event
• Log every lead with its score and follow-up status for post-event review
• Hand warm leads to a slower nurture sequence instead of dropping them

What the existing event-lead workflows miss

The BANT qualification template on n8n.io (Automate Lead Qualification & Multi-Channel Follow-up with AI) scores leads well with Gemini and routes hot/mid/cold across email and WhatsApp. But it's built for a web form, not an event. Its own description has no event triggers, no badge-scan import, and no post-event timeline. A conference lead isn't a contact-form fill; the context is different and the urgency is higher.

The general follow-up template (Automated Lead Follow-up System with Gmail, Calendar & Sheets) polls hourly and sends a single follow-up after 24 hours. For an event, an hourly poll is already too slow, and one touch isn't a sequence. It also has no AI personalization beyond a "customization" note and no conversation-context handling. So the gap is clear: an event-native, webhook-triggered, AI-scored follow-up that moves in seconds and reads like it remembers the booth chat.

Here's the stance that matters: the conversation note is the most valuable field on the lead, and almost every event workflow ignores it. Title and company are commodity data you could buy. What the rep jotted down ("comparing vendors, decision in Q3") is gold, and feeding it into the scoring prompt is what separates a follow-up that lands from a templated blast.

The Event Follow-Up Pipeline

Trigger (badge scan webhook)
  → Process (dedupe + AI score 1–10)
    → Route (hot 7+ / warm / cold)
      → Action (instant email + Slack alert / nurture / log)

1. Collect the badge scan

A n8n-nodes-base.webhook node receives the lead. Any badge scanner, conference app, or booth tablet that can POST JSON will work: name, title, company, and the all-important conversation notes. No special connector needed. The reps don't change their workflow; they scan as usual, and the JSON lands in n8n.

Worth flagging: at a busy booth, scans arrive in bursts. The Webhook node handles concurrency fine, but if your scoring path is slow, set the webhook to respond immediately and process after. The booth tablet shouldn't hang waiting for an LLM call.

2. Process and score

First a n8n-nodes-base.code node (v2, jsCode) normalizes the payload and runs a dedupe check, since at a multi-day event the same prospect gets scanned twice constantly. Then the @n8n/n8n-nodes-langchain.openAi node (v2.1) scores the lead 1–10 and drafts a subject line and email body that reference the actual conversation. The output sits at $json.output[0].content[0].text, not the deprecated n8n-nodes-base.openAi path. Parse the result with a second Code node so the score is a number the next node can compare.

3. Route by score

A n8n-nodes-base.switch node splits on the score. Seven and up is hot and gets the instant treatment. The middle band goes to a nurture queue for a human to review later that day. The low band gets logged and left alone. Don't auto-email a cold lead from an event; a generic follow-up to someone who barely stopped at the booth reads as spam.

4. Act on hot leads

Hot leads get two things at once. A personalized follow-up email goes out immediately with a scheduling link, and a n8n-nodes-base.slack alert fires to the rep who scanned them. The rep sees the lead while they still remember the face. That's the whole point. A lead worked within the hour converts at a wholly different rate than one worked next week.

5. Log and review

Every lead, with its score, status, and email-sent flag, appends to Google Sheets via n8n-nodes-base.googleSheets. After the event, that sheet is your debrief: which booth conversations scored highest, which reps captured the best leads, what the response rate was. Without the log, the post-event review is guesswork.

Implementation patterns

Pattern 1, instant hot-lead email. Skip the queue for high scorers. The moment a 9/10 lands, the email goes. Speed is the differentiator at an event.

Webhook → Code: score
  → IF score >= 7
    → OpenAI: draft email → Send → Slack alert

Pattern 2, conversation-aware prompt. Pass the rep's notes verbatim into the scoring prompt. The model weights "ready to buy" notes far higher than a junior title, which is the judgment a flat rules engine can't make.

Pattern 3, event-scoped dedupe. Key the dedupe on contact plus event ID, not contact alone. A prospect you met last year and again this year is a fresh conversation, not a duplicate.

n8n nodes you'll use most

Getting started

1. Add a Webhook node and grab the test URL; point your badge scanner or booth form at it.
2. Add a Code node to normalize the payload and dedupe on contact plus event ID.
3. Add the @n8n/n8n-nodes-langchain.openAi node; prompt it for a 1–10 score plus subject and body using the conversation notes.
4. Parse the response with a second Code node so the score is numeric.
5. Split on a Switch: 7+ to the hot branch, the rest to nurture or log.
6. On the hot branch, send the email and fire a Slack alert to the scanning rep.
7. Append every lead to Google Sheets for the post-event review.

The scoring half of this is the same pattern covered in n8n lead scoring automation, which goes deeper on prompt design and the score bands.

Captured leads still need a place to live and a sequence to work them. The handoff in n8n lead capture to CRM keeps the scored contact moving into your pipeline, and the AI Lead Scoring & Email Routing template covers the routing fan-out once the event is over. The booth is the easy part; the follow-up is where deals are won or dropped.