Sort an inbox into actions, not folders
An inbox turned into a short list of actions, each linked back to the message it came from. Built for someone whose inbox is a to-do list with no order.
Gmail
Notion
5 steps2 integrationsRuns on demand
An inbox is a to-do list with no order. What it costs while the work is still done by hand.
- 01Messages that need action look like messages that do not.
- 02Filing is not the same as deciding.
- 03The same thread gets reopened four times.
- Read inbox38 messages · last 7 days
- Group by ask9 need action · 29 do not
- Draft tasks9 tasks · owner and due
- Review list8 kept · 1 dropped
- Create taskscreate_page · 8 rows
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the messages in the period.Gmail
- 02Group them by what they actually require of you.ModuleX
- 03Draft the tasks for the ones that need doing.ModuleX
- 04Review before anything is created.ModuleX
- 05Create the tasks in your tracker.Notion
The workflow is an editable graph. Reading runs freely; review before anything is created waits for your opt-in approval until you loosen it. The graph is the receipt.
Actions, not folders. Paste this into ModuleX chat, or hit Use this workflow.
sort an inbox into actions, not folders: read the messages in the period; group them by what they actually require of you; draft the tasks for the ones that need doing; review before anything is created. 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.
Sort an inbox into actions, not folders. An inbox turned into a short list of actions, each linked back to the message it came from.
- notion · create_page
An inbox turned into a short list of actions, each linked back to the message it came from.
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 mail and creates tasks elsewhere.