Automating your inbox
Outline published The outline is settled, the content isn't written yet.
A flow running on your own machine that sorts your inbox and summarizes it daily — and that you can modify without breaking.
Tell me what's missing
- What you need before starting
- No code. You need to be able to install n8n somewhere, or already have an instance.
- Time
- About 3 hours
- Format
- Not settled yet. Video, text or both: it gets written here before the course ships, not after.
What you leave with
- The complete plan, from install to a flow that runs without you
- The flow file to import — the same one that lives in the shop
- The sorting rules that work with no artificial intelligence at all
- The arithmetic of what one AI call per email costs, with real numbers
- Where to put your credentials, and where never to put them
- A read-only variant so you can try everything without moving anything
How you know it's done
At seven in the morning an email is waiting: what came in overnight, already sorted, and the rest boiled down to ten lines. You started nothing. And when you change a rule, you know which one and why.
The outline
Every step ends with something you can watch work. That's the bottom line of each one.
-
Installing n8n without pain
On your machine or on a server. What that changes for your data, and why I recommend starting local.
n8n opens in your browser, and it is still running after the machine reboots.
-
Your first flow, in five nodes
Trigger, condition, action. Enough to grasp the logic before touching anything that matters.
A flow fires on its own, writes a line somewhere, and you can point at which one.
-
Connecting your inbox
Credentials: where they live, who can read them, and how not to put them somewhere you'll regret.
The flow reads your email, and your password is written nowhere inside the flow.
-
Sorting without mistakes
Simple rules first. Most useful sorting happens with no AI at all, and it's more reliable that way.
A hundred of yesterday's emails go back through the flow, and you count the mistakes instead of guessing at them.
-
When AI is worth it
And when it costs more than it returns. The daily summary is a good case; strict sorting isn't.
The daily summary lands in your inbox, and you know what it cost, provider by provider.
-
Letting it run
Watching a flow without thinking about it: what should alert you, and what should stay quiet. An automation you check daily isn't one.
You don't open it all week, and it writes to you only on the day it breaks.
On your bench
- With the kit
- The template in the shop is where the course lands, not what it needs to start. You can build it yourself by following the steps.
- Without the kit
- Nothing to buy. You need a machine that stays on — an old laptop at the back of a closet does the job.
The tools
- A machine that stays on, or a small rented server
- An inbox you are allowed to connect — not your employer's
- An API key if you want the daily summary; the sorting itself needs none
- Somewhere to keep a copy of the flow before you change it
The hardware
This kit has a coursen8n template — inbox triage
An n8n flow that reads your inbox, sorts what comes in, and summarizes the rest once a day. Import as is.
How this course is made
The outline and the first drafts are built with AI tools. Every step is then assembled, tested on a real robot and corrected by hand before publication. That's the part that takes time, and it's the part that counts. We say so because it's the business we're in: showing how we use these tools beats selling them in the abstract.