Wake up to a sorted inbox, waiting reply drafts and a checked calendar
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Methods
Have a scheduled agent sort your work email overnight and check tomorrow's calendar
Steps
- Decide the buckets and the VIP list. Write down four buckets, the senders that must always reach you, and the actions the agent may take. Most people start with draft and label only. Check: You have a one-page rule list that fits in the prompt.
- Connect email and calendar with the narrowest access. Connect Gmail and Calendar through your agent's connector or MCP server. Where you can, grant read, draft and label only. On Claude, keep the per-send approval switched on. In n8n, simply do not add Send or Delete nodes. Check: The agent can list yesterday's emails and tomorrow's events, and has no tool that sends or deletes.
- Run the prompt once by hand on a small window. Run the default prompt on the last 24 hours only. Compare every bucket with what you would have chosen. People who tested first on a small inbox still hit problems later, so this check does not prove it is safe at scale. Check: No email you care about is in FYI or Noise, and every draft sits in the right thread.
- Tune voice and rules. Fix wrong buckets by adding rules, not by arguing with the agent. If drafts do not sound like you, point it at a larger sample of your sent mail. Check: You would send at least half of the drafts with light edits.
- Schedule it. Set the run for an hour before your day starts. Send the brief to one place you already read, such as a Slack DM or a note. Check: The next morning the brief arrives at the set time without you opening the app.
- Review and send yourself. Read the brief, open each draft, fix [CHECK] markers and send. Act on the "Suspicious" list by hand. Check: You sent or deleted every draft and the brief has no open items.
- Watch for silent breakage. Connectors and APIs change. Check once a week that drafts still land in the right thread and the brief still covers every account. Check: This week's brief has the same sections and accounts as last week's.
- Optional: The source includes agent prompts for Claude Cowork, Claude Code, Lindy and n8n, and a list of what goes wrong; they are linked there, not copied here.
- Note: Steps quoted from the Agents Handbook (CC BY 4.0). The agent reads private mail, so give it draft and label access only and never let it send. Check your company's policy on AI access to work email first.
Run this method with your agent
Download .mdCopied 0
--- name: "triage-work-email-overnight-and-prep-tomorrow-method" description: "Use when you need to Wake up to a sorted inbox, waiting reply drafts and a checked calendar. Have a scheduled agent sort your work email overnight and check tomorrow's calendar" --- # Have a scheduled agent sort your work email overnight and check tomorrow's calendar Job: [Wake up to a sorted inbox, waiting reply drafts and a checked calendar](https://aiagents.org/canai/triage-work-email-overnight-and-prep-tomorrow) ## Need - AI agent ## Steps 1. Decide the buckets and the VIP list. Write down four buckets, the senders that must always reach you, and the actions the agent may take. Most people start with draft and label only. Check: You have a one-page rule list that fits in the prompt. 2. Connect email and calendar with the narrowest access. Connect Gmail and Calendar through your agent's connector or MCP server. Where you can, grant read, draft and label only. On Claude, keep the per-send approval switched on. In n8n, simply do not add Send or Delete nodes. Check: The agent can list yesterday's emails and tomorrow's events, and has no tool that sends or deletes. 3. Run the prompt once by hand on a small window. Run the default prompt on the last 24 hours only. Compare every bucket with what you would have chosen. People who tested first on a small inbox still hit problems later, so this check does not prove it is safe at scale. Check: No email you care about is in FYI or Noise, and every draft sits in the right thread. 4. Tune voice and rules. Fix wrong buckets by adding rules, not by arguing with the agent. If drafts do not sound like you, point it at a larger sample of your sent mail. Check: You would send at least half of the drafts with light edits. 5. Schedule it. Set the run for an hour before your day starts. Send the brief to one place you already read, such as a Slack DM or a note. Check: The next morning the brief arrives at the set time without you opening the app. 6. Review and send yourself. Read the brief, open each draft, fix [CHECK] markers and send. Act on the "Suspicious" list by hand. Check: You sent or deleted every draft and the brief has no open items. 7. Watch for silent breakage. Connectors and APIs change. Check once a week that drafts still land in the right thread and the brief still covers every account. Check: This week's brief has the same sections and accounts as last week's. 8. Optional: The source includes agent prompts for Claude Cowork, Claude Code, Lindy and n8n, and a list of what goes wrong; they are linked there, not copied here. 9. Note: Steps quoted from the Agents Handbook (CC BY 4.0). The agent reads private mail, so give it draft and label access only and never let it send. Check your company's policy on AI access to work email first. ## Credit Method author Agents Handbook editors (CC BY 4.0) Source: https://agentshandbook.com/p/triage-work-email-overnight-and-prep-tomorrow
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/triage-work-email-overnight-and-prep-tomorrow - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "triage-work-email-overnight-and-prep-tomorrow",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}