Automated Cold Email Follow Up Sequence from Google Sheets
N8N
Project's Category
Intro
This one runs every hour, skips weekends, and works through a Google Sheet of email sequences to send first touch messages and automatic follow ups until someone actually replies.
Problems
Chasing cold email leads by hand meant someone had to remember exactly who got a first message, who needed a follow up, and who had already replied. Follow ups either went out too late or never went out at all.
Solutions
We built an n8n workflow that checks a Google Sheet every hour, skipping weekends, and sends the first message in the sequence to anyone who hasn't been emailed yet. For everyone already in the sequence, it reads the thread, checks whether every previous message was automated and unanswered, and whether enough time has passed to send the next one. A sub workflow handles the actual sending, replying to the existing thread if there is one or starting a new message if not, and the sheet gets updated with the last contacted time after every send.
Final Thoughts
Splitting the sending logic into its own sub workflow keeps the first touch and follow up triggers from duplicating the same Gmail code twice. It also means whoever reads this later only has to understand one place where emails actually go out.
Automated Cold Email Follow Up Sequence from Google Sheets
N8N
Project's Category
Intro
This one runs every hour, skips weekends, and works through a Google Sheet of email sequences to send first touch messages and automatic follow ups until someone actually replies.
Problems
Chasing cold email leads by hand meant someone had to remember exactly who got a first message, who needed a follow up, and who had already replied. Follow ups either went out too late or never went out at all.
Solutions
We built an n8n workflow that checks a Google Sheet every hour, skipping weekends, and sends the first message in the sequence to anyone who hasn't been emailed yet. For everyone already in the sequence, it reads the thread, checks whether every previous message was automated and unanswered, and whether enough time has passed to send the next one. A sub workflow handles the actual sending, replying to the existing thread if there is one or starting a new message if not, and the sheet gets updated with the last contacted time after every send.
Final Thoughts
Splitting the sending logic into its own sub workflow keeps the first touch and follow up triggers from duplicating the same Gmail code twice. It also means whoever reads this later only has to understand one place where emails actually go out.
Building the automation systems that handles business processes.
Clear Communication
Reliable
Professional
Reliable Quality
Building the automation systems that handles business processes.
Clear Communication
Reliable
Professional
Reliable Quality
