Email digests
Sends one short summary of what arrived overnight, split by what needs a decision and what owes a reply.
Overnight mail, send one digest grouped by decision needed and reply owed, and add anything owed a reply to the task list.
| Group | What goes in |
|---|---|
| Decide | Anything waiting on my answer |
| Reply | Messages that owe a reply today |
| FYI | Everything else, one line each |
The job, and what good looks like.
Mail that lands overnight competes with the morning for attention, and the message that needed a decision is usually read third. The digest replaces the inbox as the starting point. On a fixed morning schedule, the workflow collects everything that arrived overnight and splits it into three short lists: needs a decision from me, needs a reply from somebody, and needs nothing today. Each line carries the sender, the ask in one sentence, and the date it was sent, so a decision can be made without opening the message. Anything waiting on a reply becomes a task with a date, and if it is still unanswered a week later the sender is named again in the next digest. A rule sends newsletters, receipts, and calendar confirmations to their own label so they never reach the summary at all. The full mailbox stays open for searching, but it is not where the day gets planned. A person still decides which decisions are worth making before the day starts, which senders get a real answer, and how blunt a reminder is allowed to be.
When it is handled
- Overnight mail read once, not all morning
- Every waiting reply has a date
- Decisions separated from reading
- Digest arrives before the first meeting
Works with tools like
- Gmail
- Superhuman
- Todoist
- Slack
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
You stay in charge.
At every step.
It sorts and reminds. You decide what to do.
- It never replies for you
Digests and reminders come to you. Anything that would send a message waits for your OK.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only what you connect
Each automation reaches only the inbox, calendar and notes you give it.
Gmail Morning Brief
Approve before it sends the email and saves the document?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Built-in rules in your email and calendar
Filing messages by sender or subject.
They can't read what a message asks for, or follow up on it.
Flowchart automation tools
Connecting apps if you build and maintain the flow.
Every exception becomes another branch.
AI chat assistants
Summarizing when you ask.
Nothing happens until you remember to ask.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.