Somewhere in your sent folder is a deal that went quiet in March. They were interested. You meant to bump it. It is now July, and re-opening feels stranger every week you do not.
What it does
The deal you make with the robot: any thread you are waiting on, you label “waiting”. Each morning the workflow checks those threads. Three days without a reply and AI writes a short bump in your voice, two or three sentences that reference what you actually asked, and drops it into your drafts as a reply in the thread. You read it over coffee, hit send or fix a word first, done. When the other side replies, the label comes off by itself.
Nothing here auto-sends, on purpose. A follow-up carries your name into someone’s inbox; a human should look at it for four seconds first. The robot’s job is remembering and writing the first draft, which were the two parts you kept not doing.
How it works
A morning schedule reads the waiting label. Threads where the last word was yours and old enough get handed to the AI step with the recent context and a strict style: no guilt-tripping, no “just checking in” as the entire message, end with an easy question. The draft attaches to the thread. Threads that got an answer get the label removed and never reach the AI at all.
Setup
- Import the workflow file into your n8n instance.
- Create a waiting label in Gmail.
- Connect an AI provider key and paste one real follow-up email you have written, so the drafts learn your voice.
- Label a few threads you are waiting on.
- Check your drafts folder tomorrow morning.
The template runs on n8n, any recent version, cloud or self-hosted. Every place that needs one of your accounts is marked with a note inside the workflow.
Get the workflow
Rather have this running in your business without touching a single node? That is the actual job. Write to hello@nurho.net or start with the ROI calculator to see if it is even worth automating.