Automated 126 Mail Stale Thread Chasing
Every morning, WebRun opens 126 Mail, finds threads that have gone 3 days without a reply from you, drafts a reply for each one and leaves it unsent, checks Gmail for any related earlier thread with the same contact, and logs the chase list to Airtable.
How do I chase 126 Mail threads I haven't replied to yet?
WebRun checks 126 Mail every morning for threads that have gone 3 days without a reply from you, drafting a reply for each and leaving it unsent. It checks Gmail for related history with the same contact and logs the chase list to Airtable, so nothing waiting on you gets forgotten.
- Threads waiting 3 days or more get a drafted reply ready to send
- Related Gmail history gets checked before you reply
- Every stale thread is tracked in one Airtable base
Built for freelancers · customer facing teams · sales reps · solo founders
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
mail.126.comin a real browser with your saved login - no setup, no API keys. -
1
126 Mail - find threads waiting on a reply
- Open 126 Mail and find threads where the last message is not from you
- Filter to ones with no reply after 3 days
- Draft a reply for each one and leave it unsent
Done when Every thread stale 3 days or more has a drafted reply waiting.
-
2
Gmail - check for related context
gmail.com
WebRun opens Gmail to check for related context. - Search Gmail for any earlier thread with the same contact
- Note anything relevant that might inform the drafted reply
- Skip the check if no related history exists
Done when Each stale thread has been checked for related Gmail context.
-
3
Airtable - log the chase list
airtable.com
WebRun opens Airtable to log the chase list. - Add a record for each stale thread with the sender, subject, and days waiting
- Note any related context found in Gmail
- Mark it open until the drafted reply is sent
Done when Every stale thread this run has an Airtable record.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it send the reply for me?
No. WebRun only drafts a reply and leaves it unsent in 126 Mail. You read it, edit it if needed, and hit send yourself.
How does it decide a thread is stale?
It checks whether the last message in the thread is from someone else and how many days have passed, using the 3 day threshold you set.
Why check Gmail too?
If the same contact has emailed you elsewhere, that history can make the drafted reply more useful, so it's worth a quick check before you send.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.