Follow-Up Agent (n8n) — STRUCTURE SUMMARY 🎯 What this agent does Tracks who you contacted Knows who replied vs who didn’t Sends smart follow-ups Stops automatically when there’s a reply So you never chase manually and never sound spammy. 🧠 Agent Logic (High Level) “If someone hasn’t replied in X days, send a context-aware follow-up. If they replied, stop everything.” That’s it. Everything else is implementation. 👏🏻n8n STRUCTURE (Simple & Real) 1.Trigger Cron Node Runs every day (or every 12 hours) Purpose: → “Check who needs a follow-up today” 2.Source of Truth Google Sheets / Airtable / Notion Node Sheet contains: Name Email / DM handle Last message sent date Reply status (Yes / No) Follow-up count Purpose: → Agent always knows the current state 3.Filter Logic IF Node Conditions: Reply = ❌ No Days since last message ≥ 2 (or your rule) Follow-ups sent < 3 Purpose: → Prevents annoying people → Prevents infinite follow-ups 4.Context Builder Set Node Creates context like: Who this person is What you already sent What follow-up number this is Purpose: → This is why your message doesn’t sound robotic 5.LLM Node (Message Writer) Prompt logic: Write ONE short follow-up Reference previous message No pressure Natural tone No CTA overload Purpose: → Message feels human, not “Day 3 Follow-Up Template #7” 6.Send Message Gmail / LinkedIn / WhatsApp Node Sends the follow-up. Important rule: → ONE message per run per person (no machine-gun behavior) 7.Update Memory Google Sheets / DB Node Updates: Last message date = today Follow-up count +1 Purpose: → Agent remembers what it did 8.Reply Stopper (Optional but Powerful) Email Trigger / Webhook If reply detected: Set Reply = ✅ Yes Kill all future follow-ups Purpose: → This is what separates amateurs from pros. 🎉 Questions:- 1. Suggestions to add-on? 2. Is it felling like automated now? 3. How much ROI you're expecting from this?

Event ticket processing. 360 registrations annually. Manual data entry consuming 180 hours. Built n8n workflow. Zero manual entry. Automatic QR delivery. THE EVENT PROCESSING PROBLEM: Every confirmation email manual. Event coordinator downloading PDF. Typing attendee details into database. Entering event information - name, date, time, venue location. Typing ticket details - type, number, seat assignment, price, quantity. Opening QR code generator website manually. Creating QR code. Downloading image. Composing confirmation email. Attaching QR code. Sending. Checking special requirements manually. Noting dietary restrictions for catering. Flagging accessibility needs for venue. 30 minutes per registration. 360 annually = 180 hours. Audit errors - 45 missed QR deliveries. 67 special requirements not flagged. 89 QR codes with wrong ticket numbers. 18.3% error rate. THE n8n AUTOMATION: 9-node workflow with 2-path email routing: Node 1 - Gmail Trigger: Monitors ticket confirmations Node 2 - Get Email: Downloads with PDF attachment Node 3 - Prepare Binary: Formats document Node 4 - Extract Data: Pulls attendee/event/ticket/special requirements Node 5 - Process Ticket: Calculates timeline, generates check-in code Node 6 - Log Database: Updates registration tracking Node 7 - Generate QR: Creates QR code image from ticket data Node 8 - Prepare QR: Formats for email delivery Node 9 - Email Router: QR code email OR no-email alert EXTRACTION: Attendee - name, email, phone Event - name, date, time, venue location Ticket - type, number, seat/section/row, price, quantity Special - dietary restrictions, accessibility needs, VIP access PROCESSING LOGIC: ```javascript // Timeline calculation const daysUntil = (eventDate - today) / (1000 * 60 * 60 * 24); const isToday = daysUntil === 0; const isSoon = daysUntil > 0 && daysUntil <= 7; // Priority determination let priority = 'Normal'; if (isToday) priority = 'High'; if (isSoon) priority = 'Medium'; // QR code generation