PERSONAL PRODUCTIVITY

On-Demand Focus-Block Defender

Triggered manually for any chosen week, finds the largest unbooked gaps each day and creates protected focus-block holds on the calendar.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggermanual
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerManual run for target week
  • ActionRead target week's eventsGoogle CalendarGoogle Calendar
  • LogicFind largest gap and check minimum length
  • ActionCreate protected focus-block holdsGoogle CalendarGoogle Calendar
  • OutputReport reserved and unfixable days to SlackSlack

What it does

Turns auditing into action. On demand for a target week, it scans each day for the biggest available gap, and where a gap of at least the desired length exists, it books a held focus block directly on Google Calendar marked as busy. For days too fragmented to protect, it flags them instead. A Slack message summarizes what was reserved and what needs manual rescheduling.

When to use it

Use it before a heads-down week, sprint, or crunch when you want focus time defended proactively rather than hoping gaps survive. Run it manually whenever you need to claim back your week in one move.

How it works

  1. 1A manual trigger runs with a chosen target week.
  2. 2The flow reads all events for that week from Google Calendar.
  3. 3A logic step finds each day's largest free gap and decides if it meets the minimum length.
  4. 4For qualifying days it creates a protected focus-block event on the calendar.
  5. 5Days that can't be protected are recorded as unfixable.
  6. 6A Slack message reports reserved blocks and flags the days needing manual attention.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.