Protect the time you actually need to work
Focus blocks on the calendar before the week fills, chosen by you from what was actually free. Built for anyone whose calendar fills with meetings before they can plan the week.
Google Calendar
4 steps1 integrationRuns on demand
Open calendar space reads as available. What it costs while the work is still done by hand.
- 01Open calendar space is treated as available by everyone else.
- 02Focus time is booked over because it was never on the calendar.
- 03The week is planned by whoever books first.
- Read week22 meetings · Mon to Fri
- Find gaps6 blocks · 90 min or longer
- Propose blocks4 picked · Tue, Wed, Fri
- Add events4 held · marked busy
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the coming week's commitments.Google Calendar
- 02Find the remaining blocks that are long enough to be useful.ModuleX
- 03Propose the focus blocks for your week.ModuleX
- 04Add the approved blocks to the calendar.Google Calendar
The workflow is an editable graph. Reading runs freely; propose the focus blocks for your week waits for your opt-in approval until you loosen it. The graph is the receipt.
Focus time, on the calendar. Paste this into ModuleX chat, or hit Use this workflow.
protect the time you actually need to work: read the coming week's commitments; find the remaining blocks that are long enough to be useful; propose the focus blocks for your week; add the approved blocks to the calendar. 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.
Protect the time you actually need to work. Focus blocks on the calendar before the week fills, chosen by you from what was actually free.
- google calendar · create_event
Focus blocks on the calendar before the week fills, chosen by you from what was actually free.
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 works with the space that is already free.