Event follow up engine
Attendee data comes in from the event platform, each person is grouped by what they attended, Claude writes a follow up that refers to it, and the batch goes out within a day while people still remember the event.
- Trigger
- event export or webhook
- Window
- within 24 hours
- Attendees
- 300+ per event
- Spacing
- 30 s between sends
Why it exists
Events produce warm leads and then the follow up is slow, generic or doesn't happen. Writing 300 personal emails by hand isn't going to happen, so teams send a blast or nothing.
How it runs
Import
Attendee data arrives from the platform's export or a webhook: name, email, sessions, notes.
Segment
People are grouped by the sessions they attended and the topics they engaged with.
Write
Claude writes each follow up from the person's sessions and notes, so it refers to what they actually saw.
Send
The batch goes out within 24 hours with 30 seconds between sends.
Log
Each contact is recorded with engagement level, sessions and the follow up sent, ready for sales.
Flag
The people who engaged most are flagged for a personal follow up by the team.
What came out of it
Everyone hears back within a day with something that refers to their event, and the team gets a short list of who to call personally.
Notes
Built to prove the pattern. The segmenting is only as good as the attendance data the event platform exports, so the first thing to check on a new client is what their platform actually records.
Stack
- n8n
- Claude API
- Gmail
- Airtable
- Webhooks
Want something like this built?
Tell me what you're trying to automate. Most things can be built in a week or two.