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:-
- Suggestions to add-on?
- Is it felling like automated now?
- How much ROI you're expecting from this?