Will the AI ever send an email without me?

No. The workflow is built around drafts: the AI can read, label, archive and draft, and sending always stays a human action.

What happens to something the AI mis-files?

Labels and archiving are reversible, and the AI reports what it did each run. Correct it once and fold the correction into the rules.

AI Use Cases

Quick winBusiness + PersonalSaves 2 to 4 hours per week

Inbox tidy-up

AI triages your inbox: labels and archives newsletters, surfaces what matters and drafts replies for you to review. Drafts only, never auto-send.

The problem

Email arrives faster than anyone can sort it. Newsletters bury client messages, the same three kinds of request get retyped answers every week, and "inbox zero" becomes a weekend job.

The workflow

1
Connect your mail
Add the Gmail or Outlook connector with permission to read, label and draft (not send).
2
Set the triage rules
Tell the AI how you sort: what gets archived, what gets labelled for later, what needs a reply today.
3
Run the tidy-up
The AI sweeps the inbox: newsletters archived, messages labelled, a short list of what actually needs you.
4
Review the drafts
For routine requests, the AI leaves a draft reply in the thread. You edit and send; nothing goes out on its own.

Start here

Once your connectors are set up, this prompt kicks the whole workflow off. Adjust the details to match your business.

Paste this into your AI tool

Tidy my inbox. Archive newsletters and automated notifications, noting anything genuinely useful first. Label what remains as 'needs reply', 'waiting on others' or 'FYI'. For every routine 'needs reply', draft a reply in the thread for my review. Never send anything. Finish with a summary of what you did and a short list of what actually needs me.

The outcome

An inbox where everything waiting for you actually needs you, with routine replies already drafted.

Time saved: 2 to 4 hours per week

What it needs

The connectors this workflow uses, and how it runs on each AI platform.

Connectors

Gmail optional Outlook optional

Works on

Last verified 18 October 2026

Copilot (free)	Not possible	The consumer app cannot add custom MCP servers.
Copilot Pro	Not possible	Drafted, to verify.
Microsoft 365 Copilot	Build required	Via declarative agents; MCP tool calls consume Copilot Credits.
Copilot Studio agents	Build required	Needs a Copilot Studio licence.
Claude Free	Works natively	Limited to 1 custom connector.
Claude Pro/Max	Works natively
Claude Team/Enterprise	Admin setup needed	Owners add custom connectors.
Claude Code	Works natively
Gemini Enterprise	Admin setup needed	Custom MCP blocked by default org policy; not on Business edition.

Who it's for

Retail & eCommerce Professional Services Public Sector Healthcare & Life Sciences Charities & Non-profit Manufacturing & Logistics Technology & Software Education Personal/Household Development/Engineering Finance Operations Sales Marketing HR/People Leadership Customer Service Personal

The reusable skill

The reusable recipe: separate triage (safe to automate) from sending (keep human). Give AI the labels and the rules, let it sort and draft, and keep the send button yours. The drafts-never-send rule is what makes this safe enough to run daily.