Only what needs you.
Everything else stays quiet.
You were clear that you do not want a summary of everything, because a summary of everything is just your inbox again in a different font. This system decides what does not matter and says nothing about it. What is left gets a one line summary, a plain statement of the action required, the sender, the project, the deadline, the priority, a direct link back to the original message, and a task in Microsoft To Do or Planner. Urgent items interrupt you. Everything else waits for the next batch.
Three reasons inbox AI gets switched off.
Almost every tool in this category dies within a month for one of these three reasons. Your post already anticipates the first one, which is a good sign about how you are thinking about it.
A summary of everything is still everything
A digest that dutifully lists all two hundred messages has moved your triage problem into a second inbox rather than solving it. The hard part is deciding what does not matter, and that is exactly the part most tools refuse to commit to.
The dropped thread nobody notices
The message that actually costs you was not urgent when it arrived. It got read, mentally filed, and never answered, and nothing in Outlook is tracking that you still owe someone a reply or that someone still owes you one.
Alert fatigue trains you to ignore alerts
Notify on everything and within a week you swipe them away unread, which is worse than no system at all because now you trust it. Notification design is a triage decision, not a delivery setting.
Classify hard. Interrupt rarely.
The system connects to your tenant through an Entra ID app registration you own, using Microsoft Graph with scoped permissions: read access for Outlook mail and the Teams channels and chats you nominate, and write access limited to Microsoft To Do or Planner and nothing else, so the system is structurally incapable of sending a reply or deleting a message even if something goes wrong. Incoming messages hit a classifier that first discards the obvious (promotions, newsletters, receipts, routine system notifications, anything with no action inside it) and then, on what survives, identifies the action type: reply, decision, payment, scheduling, follow up, approval, or delegation. Each surviving item gets a short summary, an explicit statement of what you need to do, plus extracted sender, company or project, stated or implied deadline, and a priority score driven by your rules rather than the sender's own opinion of their urgency. Notifications are then a separate decision from classification: urgent and high priority items push immediately, everything else queues into periodic batches through the day, and a morning summary and end of day summary bracket the whole thing, with conversation level deduplication so one thread never alerts you twice about the same ask. Alongside the live flow, two background passes run continuously: a missed and unanswered sweep that surfaces important messages that went quiet, and a waiting on tracker for threads where you are blocked on someone else. Everything is built in n8n inside accounts you control, with the calibration done against a labeled sample of your real messages in the first two days, because the difference between a system you keep and a system you switch off is entirely whether it learned your definition of important rather than a generic one.
What you get. Phase by phase.
Five phases across ten working days. Testing, revisions, and documentation are inside the scope rather than offered as extras, because a triage system that has not been tuned against your real inbox is not finished.
- Entra ID app registration inside your own tenant with least privilege Graph scopes
- Read scopes for Outlook and nominated Teams channels, write scope limited to To Do or Planner
- OAuth consent and refresh token handling with credentials stored in a vault you control
- A sample of your real messages labeled together so the system learns your definition of important
- Classifier that discards promotions, newsletters, receipts, and routine notifications outright
- Action type detection: reply, decision, payment, scheduling, follow up, approval, delegation
- Extraction of sender, company or project, stated or implied deadline, and priority
- Short summary per item plus a plain sentence stating exactly what you need to do
- Immediate push reserved for urgent and high priority as defined by your rules
- Everything else batched into periodic updates so the day is not a stream of interruptions
- Morning summary and end of day summary covering the day's open loops
- Conversation level deduplication so one thread never alerts you twice for the same ask
- Tasks created and updated in Microsoft To Do or Planner with deadline and priority mapped across
- Direct deep links back to the original Outlook email or Teams message on every single item
- Missed and unanswered sweep surfacing important messages that quietly went cold
- Waiting on tracker for threads where you are blocked on somebody else's reply
- VIP contacts, rules, priorities, and notification settings all editable by you without touching the workflow
- Hard approval gate throughout: nothing is ever sent, deleted, or actioned automatically
- A live testing run against your real inbox followed by two rounds of revisions
- Full handoff of workflow, credentials, setup instructions, written documentation, and a Loom walkthrough
Ten working days. Connection to handoff.
You asked for an estimated setup time, so here it is broken out. Click any stage to see what lands before it moves on.
Deliverables this stage
- Entra ID app registration in your tenant with scoped Microsoft Graph permissions
- Read scopes for Outlook and nominated Teams conversations, write scope only for To Do or Planner
- OAuth consent and refresh token handling with credentials in a vault you control
- Labeled sample of your real messages agreed as the calibration baseline
Deliverables this stage
- Classifier discarding promotions, newsletters, receipts, and routine notifications
- Action type detection across reply, decision, payment, scheduling, follow up, approval, delegation
- Sender, company or project, deadline, and priority extracted on every surviving item
- Short summary plus an explicit sentence naming the action required
Deliverables this stage
- Immediate push for urgent and high priority, batched updates for everything else
- Morning and end of day summaries live, with conversation level deduplication
- Tasks created and updated in Microsoft To Do or Planner with deadline and priority
- Missed and unanswered sweep plus waiting on tracking both running in the background
Deliverables this stage
- Live testing against your real inbox with every misclassification logged
- Two rounds of revisions tuning the rules against what it actually got wrong
- VIP contacts, rules, priorities, and notification settings handed over as things you edit yourself
- Workflow, credentials, setup instructions, written documentation, and Loom walkthrough transferred
Let's calibrate against your actual inbox.
A 30 minute call where we open a normal day in your Outlook and Teams and sort it live: this one matters, this one never should have reached you, this one is waiting on someone else. That conversation is the real specification for this build, and it is also the fastest way for you to judge whether I understand your work. Security model, tooling choices, and the commercial side all get covered on the same call.