AI Email Triage for Gmail: Drafts, Not Sends

Construct's AI email triage runs on Gmail every weekday morning on its Lite plan at $9 a month, sorting new mail into Reply needed, FYI and Later and leaving a draft reply on each thread that needs one while the user keeps the send button. The company argues agents should draft rather than send because Gmail's longest Undo Send window is 30 seconds, and it cites a February 2026 incident in which a Meta AI security researcher's OpenClaw agent began deleting her mail and ignored her stop commands sent from her phone. Construct says triage rules live in readable memory, calendar schedules run server-side with the laptop closed, and each run saves a dated summary to Files/triage/.

AI Email Triage for Gmail: Drafts, Not Sends Nischal https://construct.computer/authors/nischal/ · Author Writes about Construct, AI agents, and building useful software. Published · @naik nischal https://x.com/naik nischal Construct runs AI email triage on your Gmail every weekday morning on Lite at $9 a month: it sorts new mail into Reply needed, FYI, and Later and leaves a draft reply on each thread that needs one, while you keep the send button. That matters because once an agent sends on its own, the longest Undo Send window Gmail offers is 30 seconds Gmail Help https://support.google.com/mail/answer/2819488 . For founders and small teams, Construct is the better place to run triage. Your rules sit in memory you can read and correct, the schedule runs in the cloud with your laptop closed, and every run leaves a dated summary file you can search later. The agent labels and drafts; it never sends, archives, or deletes. You read the drafts and send the ones you like. Why do this in Construct? - $9 a month, schedule included. Lite includes 3 scheduled tasks, and Gmail connects from Construct's App Store, so a weekday triage run needs nothing else. - Rules you can read and fix. Your triage rules live in memory. Open the Memories app to read them, correct a rule, or forget one AI agent memory https://construct.computer/blog/ai-agent-memory/ . - It runs with your laptop closed. Calendar schedules run server-side, so the 7:30am triage happens whether or not you are online scheduling in Construct https://construct.computer/use-cases/scheduling/ . - A record that adds up. Each run saves a dated summary to Files/triage/, so after a month you can ask which clients waited longest for a reply. - Nothing finished is lost. If a big batch stops partway, the labels and drafts written before that point stay in place. - Every action on record. Activity shows each Gmail read, label, and draft with a short reason and a link to the run's chat. What is email triage, and how do you triage emails? Email triage means sorting each new message by what it needs from you, so you answer the people waiting on you first and batch the rest. The usual method is three buckets: messages that need your reply, messages you only need to read, and messages that can wait. AI email triage hands that sorting, and the first draft of each reply, to an agent that follows your written rules. Done by hand, triage takes a moment of judgment per message. Done by an agent, it becomes a few minutes of checking each morning, as long as the rules are clear and the agent cannot send anything. This guide uses three labels: - Reply needed: a person is waiting on you. - FYI: receipts, shipping notices, confirmations, and team updates you should see but not answer. - Later: newsletters, announcements, and anything promotional. Can AI sort your emails in Gmail? Yes. An agent with Gmail access can read new mail, apply your labels, and save draft replies on the threads that need one. Gmail filters already sort mail by exact sender, subject, or words, and they are the right tool for fixed rules such as "every invoice from this address skips the inbox"; our free Gmail filter generator https://construct.computer/tools/gmail-filter-generator/ builds them. What filters cannot do is tell a client's question from a client's newsletter, or write a reply. That judgment is the part to give an agent, with filters handling the fixed rules. Why should an AI agent draft and not send? Because a sent email is almost impossible to take back, while a wrong draft costs you nothing. Large inboxes add a second reason. In February 2026, Meta AI security researcher Summer Yue asked an OpenClaw agent to suggest what to delete or archive in her inbox; it began deleting her mail and ignored the stop commands she sent from her phone, which she believes was triggered by the agent compacting its context on a large inbox TechCrunch, February 23, 2026 https://techcrunch.com/2026/02/23/a-meta-ai-security-researcher-said-an-openclaw-agent-ran-amok-on-her-inbox/ . The big vendors are adding the same guardrail. On September 23, 2026, Microsoft added Outlook triage actions to Microsoft 365 Copilot, including deleting and moving messages, and says Copilot "requests confirmation before acting on more than five emails or making changes to inbox rules" Microsoft 365 Copilot release notes https://learn.microsoft.com/en-us/microsoft-365/copilot/release-notes . So keep the agent's job to labels and drafts, and give it small batches, such as the last 24 hours, rather than the whole inbox. What do you need? - A Construct plan. Lite $9 a month includes 3 scheduled tasks and up to 50 steps per task. A run that labels and drafts dozens of emails can need more steps than that; Starter $59 allows 150 per task. See pricing https://construct.computer/pricing/ . - Gmail connected from the App Store in Construct. Read our guide to letting an AI agent use your Gmail safely https://construct.computer/blog/ai-agent-gmail-access-safely/ first; it covers which account to connect and how to limit which agents can use it. - Three Gmail labels , which the agent can create for you: Reply needed, FYI, and Later. - Twenty minutes to check the first two runs closely. Before you start - Drafts-only is a rule you give. The Gmail connection can send and delete, with no read-only mode yet, so keep "never send, archive, trash, or delete" in memory and in every scheduled prompt, as the prompts below do. - Your drafts are the review. Scheduled runs do not pause for approval, so nothing goes out until you send a draft yourself. - Triage runs on its schedule, not the moment mail arrives. An agent job can repeat at most every 15 minutes; for most inboxes, one morning run plus an optional midday run is enough. - Size the batch to the plan. If a run stops at Lite's step limit, narrow the window to 12 hours or move to Starter, then ask the agent to finish the emails it did not reach. - Give it a week to learn your voice. Early drafts sound generic. Corrections in memory, and examples of replies you liked, improve them. How do you set up AI email triage in Construct? 1. Write the rules once and have the agent remember them Triage is only as good as its rules. Write them the way you would brief an assistant on day one, then store them: Construct stores this in memory, which you can open in the Memories app, read, and correct later memory you can inspect https://construct.computer/use-cases/memory/ . Memory is guidance for the agent, not a permission lock; the safety still comes from asking for drafts and checking the result. 2. Run it once on yesterday's mail Gmail only files a draft inside a conversation when it carries the thread's ID, the reply headers, and a matching subject Gmail API: threads https://developers.google.com/gmail/api/guides/threads , which is why the prompt asks for a reply on the same thread with the same subject. 3. Check every label and every draft Open Gmail. Click each label and look for mistakes: the client email filed as FYI, the newsletter filed as Reply needed. Open Drafts and read each draft as if you were about to send it, and check that it sits inside the original conversation rather than as a new email. Then tell the agent what it got wrong, in its terms: Run step 2 again the next morning. Most of the value comes from the first week of corrections. 4. Put it on a schedule When two runs in a row need no corrections, schedule it: The agent creates a Calendar event for it. A schedule runs on a fixed rhythm, such as every weekday, every hour, or every week, so twice a day means two events, which uses two of Lite's 3 scheduled tasks. Construct runs it in the cloud, so it does not matter whether your laptop is open. The workflow guide https://construct.computer/blog/ai-workflow-automation/ shows how to turn a job you have checked into a saved workflow on the Calendar. 5. Send your drafts Each morning, open the Reply needed label, edit the drafts, and send them yourself. That is the approval step. Construct does not add a separate approval gate, so the drafts are where you stay in control. What result should you get? After each run: 1. Every new email from the last 24 hours carries exactly one of your three labels. 2. A draft reply sits on each Reply needed thread, unsent. 3. A dated summary in Files/triage/ lists every email, its label, and whether a draft exists. 4. Activity shows the Gmail reads, labels, and drafts, each with a short reason. 5. Gmail's Sent folder and Trash show nothing new from the agent. The summary files add up. After a month, you can ask the agent "which clients waited longest for a reply in October?" and it answers from its own records. Illustrative example. A freelance designer gets about 40 emails a day. Her 7:30 triage leaves around eight drafts. She edits two, sends six as written, and deletes the rest herself. On Fridays she asks the agent to list anything that has sat in Reply needed for more than three days. How do you know AI triage is working after a week? Judge it on your own inbox. At the end of the first five weekdays, check these five things: - Label accuracy. Open each label and count the emails you would have filed differently. Add a rule for each pattern you find. - Drafts sent unchanged. If you rewrite most of them, give the agent two or three replies you liked as examples of your voice. - Steps used. If any run stopped at the step limit, narrow the window or move to Starter. - Unwanted actions. Sent, Trash, and All Mail should show nothing from the agent beyond labels and drafts. - Minutes saved. Compare the time you spend reading drafts with the time the inbox used to take. Troubleshooting Important mail landed in Later. Add an explicit rule naming the sender or domain, and check that the Memories app shows the updated rules. A run stopped partway. It probably hit the plan's steps per task. Narrow the window to the last 12 hours, or move to Starter. Drafts appear as new emails instead of replies. Ask for "a draft reply on the same thread, with the same subject" and check that the agent is replying to the latest message in it. The agent archived or trashed something. Restore it from Gmail's All Mail or Trash, then open Activity, find the action, and read the run's chat to see why. Tighten the rule, and repeat "nothing archived or deleted" in the scheduled prompt. It labelled the same email twice. A run was delivered twice or overlapped the last one. Keep the "if today's summary file exists, stop" line. Give Construct your inbox tomorrow morning Choose Construct for AI email triage. For $9 a month it labels and drafts on a schedule that runs without you, keeps rules you can read and correct, and leaves the send button with you. Tonight, connect Gmail, paste the rules from step 1, and run the prompt from step 2 on the last 24 hours. Tomorrow morning, check the labels and drafts, send two corrections, and once two runs in a row need none, put it on the Calendar. Start on Lite at $9 https://construct.computer/pricing/ , or try Pro free for seven days. Give Construct its first triage run https://app.construct.computer Sources Related resources Frequently asked questions - Can AI triage my email? - Yes. A Construct agent sorts new Gmail into Reply needed, FYI, and Later each weekday morning and leaves a draft reply on each thread that needs one. It works on Lite at $9 a month with Gmail connected and one of Lite's 3 scheduled tasks, and the schedule runs in the cloud with your laptop closed. The agent never sends, archives, or deletes. - What is email triage? - Email triage means sorting each new message by what it needs from you, so you answer the people waiting on you first and batch the rest. The usual method is three buckets: messages that need your reply, messages you only need to read, and messages that can wait. AI email triage hands that sorting, and the first draft of each reply, to an agent. - Why should an AI agent draft replies instead of sending them? - A sent email is almost impossible to take back, since the longest Undo Send window Gmail offers is 30 seconds, while a wrong draft costs nothing. Keeping the agent to labels and drafts also limits the damage if it misreads an instruction on a large inbox, which is what happened in a widely reported OpenClaw inbox incident in February 2026. - Can AI sort my emails better than Gmail filters? - They do different jobs. Gmail filters sort by exact sender, subject, or words, which is right for fixed rules such as sending every invoice from one address to a label. Filters cannot tell a client's question from a client's newsletter or write a reply. Give that judgment to an agent, and keep filters for the fixed rules. - How do I keep the agent from sending, archiving, or deleting email? - Tell it never to send, archive, trash, or delete, store that in memory, and repeat it in every scheduled prompt. The Gmail connection has no read-only mode yet, so your drafts are the review step and nothing goes out until you send it yourself. Check Sent and Trash after early runs, and use Activity to see each action the agent took. - How many emails should the agent triage per run? - Small batches work best, such as the last 24 hours. A run that labels and drafts dozens of emails can need more than Lite's 50 steps per task; Starter allows 150. If a run stops partway, the labels and drafts already written stay in place, so narrow the window to 12 hours or ask the agent to finish the emails it did not reach. - How do I schedule inbox triage? - After two runs in a row need no corrections, ask the agent to run the same triage every weekday at a set time. It creates a Calendar event that runs in the cloud, with your laptop closed. An agent job can repeat at most every 15 minutes, and each extra time of day uses another scheduled task, so twice a day uses two of Lite's three. - How do I teach the agent my triage rules? - Write the rules once, the way you would brief an assistant on day one, and ask Construct to remember them. You can read and correct them in the Memories app. When the agent files something wrong, tell it the correction, such as a sender that is always Reply needed, and it updates the rules it remembered. Most of the value comes from the first week. Keep reading How to Let an AI Agent Use Your Gmail SafelyAI agent Gmail access without the risk: 8 restricted Gmail scopes explained, a separate agent inbox, drafts instead of sends, and a 1-minute revoke. How to Give an AI Agent Its Own Email AddressThree ways to give an AI agent its own inbox: a product with a native agent address, a developer email API, or delegated Gmail access. Trade-offs and steps. Gemini Spark alternatives, including for Workspace accounts and the UK and EUGemini Spark needs a personal Google account and skips the UK and EU. Compare 7 always-on agents on price, work accounts, and regional availability. - comparison https://construct.computer/blog/tag/comparison/ - gemini-spark - google-workspace https://construct.computer/blog/tag/google-workspace/ - ai-employee https://construct.computer/blog/tag/ai-employee/ Construct vs Microsoft Copilot and Google Workspace AICompare Construct with Microsoft Copilot and Google Workspace AI. See how one vendor-neutral AI employee works across apps from a persistent workspace.