Turn an overnight inbox into a short list
A short digest that names the messages needing a reply and compresses everything else. Built for anyone who opens the laptop to fifty unread messages.
Gmail
Slack
4 steps2 integrationsRuns weekdays 8am
Fifty unread, two that matter. What it costs while the work is still done by hand.
- 01Most of the fifty need nothing at all.
- 02The two that matter are somewhere in the middle.
- 03Triage by scrolling costs the first hour.

Read inbox52 unread · since 6pm
- Split by need4 need a reply · 48 info
- Summarise48 compressed to 6 lines
Send digestpost_message · replies first
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the unread messages.
Gmail
- 02Separate what needs a reply from what is only information.ModuleX
- 03Summarise the rest in a few lines.ModuleX
- 04Send the summary to you, with the must-answer items first.
Slack
The workflow is an editable graph. Reading runs freely; send the summary to you, with the must-answer items first waits for your opt-in approval until you loosen it. The graph is the receipt.
The short list. Paste this into ModuleX chat, or hit Use this workflow.

turn an overnight inbox into a short list: read the unread messages; separate what needs a reply from what is only information; summarise the rest in a few lines; send the summary to you, with the must-answer items first. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.

Turn an overnight inbox into a short list. A short digest that names the messages needing a reply and compresses everything else.
slack · post_message
A short digest that names the messages needing a reply and compresses everything else.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Assemble the evidence pack for a reviewAn evidence pack assembled from your systems, with the gaps named and assigned. Built for whoever collects the same screenshots and exports every audit cycle.
Build a one-pager on a company before you meet themA one-pager combining public background with your own record, reusable by whoever meets them next. Built for anyone walking into a meeting knowing only the company name.
Capture a request as a task without leaving the threadA task that carries the original request and links back to where it was made. Built for anyone who says yes in an email and then forgets.
About this use case.
No. It reads and reports; your inbox is untouched.