PERSONAL PRODUCTIVITY
Overcommitment guardrail before you accept a deadline
Before a new commitment gets scheduled, it tallies the focus hours already booked that week and warns you in Slack if accepting would blow past a healthy capacity.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook with a proposed commitmentHTTP webhook
- ActionTotal existing focus hours for the weekGoogle Calendar
- LogicCompare against weekly capacity threshold
- ActionIdentify a lower-priority block to swapOpenAI
- OutputSend overcommit warning with options to SlackSlack
What it does
Focus blocks only protect you if you don't pile on more than the week can hold. This workflow acts as a capacity check: whenever a new deliverable would need focus time, it sums your already-committed focus hours for that week and flags when you're about to overcommit, so you decide consciously instead of discovering it Friday at 6pm.
When to use it
For chronic over-committers and managers who want a sanity check before saying yes. Run it as the gatekeeper in front of any of the other focus-blocking workflows.
How it works
- 1A webhook fires with a proposed commitment (deliverable, effort hours, target week) from an upstream flow.
- 2The flow reads that week's calendar and totals existing focus-block hours.
- 3A logic step compares the projected total against your weekly capacity threshold.
- 4If there's room, it books the block and exits.
- 5If accepting would exceed capacity, an LLM step identifies the lowest-priority existing block as a swap candidate.
- 6A Slack message presents the overcommit warning with options to accept anyway, bump the candidate, or decline.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
Weekly Low-Attendance Recurring Meeting Auditor
Every Friday, scans the next week of recurring calendar events, flags those where confirmed attendance keeps dropping below a threshold.
Auto-decline focus-block invites unless the organizer is a VIP
Declines meetings that overlap your focus blocks by default, but routes invites from people on your VIP allowlist to a Slack approval prompt so important asks never get…
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Weekly Subscription Audit: Find Noisy Lists Worth Unsubscribing
Once a week, analyzes which mailing lists flooded your inbox and how rarely you opened them.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.