Start the day with one brief instead of five tabs
One brief covering the meetings, the messages that need a reply, and the work that is due. Built for anyone who begins the morning reconstructing the day from four apps.
Google Calendar
Gmail
Linear
Slack
5 steps4 integrationsRuns weekdays 8am
The day is spread across four apps. What it costs while the work is still done by hand.
- 01The day's shape is spread across calendar, inbox, and tracker.
- 02The first half hour goes to checking rather than deciding.
- 03Something important is always in the app you opened last.
- Read calendar5 meetings · 2 back to back
- Read inbox31 overnight · 4 need a reply
- Read tracker7 assigned · 2 due today
- Build briefone screen · 3 sections
- Send to Slackpost_message · morning DM
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read today's meetings.Google Calendar
- 02Read what arrived overnight that still needs you.Gmail
- 03Read what is assigned to you and due.Linear
- 04Assemble a single one-screen brief.ModuleX
- 05Deliver it where you start the day.Slack
The workflow is an editable graph. Reading runs freely; deliver it where you start the day waits for your opt-in approval until you loosen it. The graph is the receipt.
One brief, not five tabs. Paste this into ModuleX chat, or hit Use this workflow.
start the day with one brief instead of five tabs: read today's meetings; read what arrived overnight that still needs you; read what is assigned to you and due; assemble a single one-screen brief. 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.
Start the day with one brief instead of five tabs. One brief covering the meetings, the messages that need a reply, and the work that is due.
- google calendar · get_calendar
- linear · search_issues
One brief covering the meetings, the messages that need a reply, and the work that is due.
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 summarises.