Use cases → Email operations
Find and remove stale automated drafts
Sweep the domain for drafts left behind by retired automations before a client sees one.
| Who it is for | Anyone who has connected more than one tool to their mail over the years. |
|---|---|
| APIs | Gmail API |
| Typical scopes | gmail.modify |
The problem
Old integrations keep writing drafts long after the project that created them is dead. They sit inside live customer threads, visible to anyone who scrolls, quietly making the business look careless.
How it works
- Search drafts across the mailbox for the signature of the offending template.
- Capture which threads were affected before removing anything.
- Delete, then verify by re-fetching and expecting a not-found.
- Schedule the sweep so a returning draft proves the source is still connected.
What changes
A clean mailbox, and a standing check that tells you if the tap is still running.
Questions people ask
How do I find what is creating them?
Check the OAuth grants on the account. Anything with mail scope can write drafts, and retired tools usually still hold their grant.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Draft replies automatically in a shared inbox
A delegated service account reads an incoming enquiry, drafts a researched reply in the mailbox, and leaves it for a human to approve and send.
Triage and route inbound mail across a domain
Classify every inbound message, label it, and forward the ones that matter to the person who owns them — without touching a single mail rule.
Send mail as a shared alias from automation
Deliver notifications, confirmations and campaign replies from a branded address like support@ or updates@ without a human in the loop.