PERSONAL PRODUCTIVITY

Auto-Create Focus Blocks Around Your Busiest Days

Every Sunday it analyzes the coming week's meeting density and automatically books focus blocks on your lightest mornings, marking them busy so colleagues can't schedule over them.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Sunday schedule
  • ActionRead next week's calendar eventsGoogle CalendarGoogle Calendar
  • LogicCompute meeting density, pick lightest windows
  • ActionCreate busy focus-block eventsGoogle CalendarGoogle Calendar
  • OutputPost weekly focus-block recap to SlackSlack

What it does

This workflow plants the focus blocks for you. It reads next week's calendar, finds the days and time windows with the least meeting load, and creates protected focus-block events on those windows set to "busy" so they show as unavailable to anyone trying to book you.

When to use it

Use it if you keep meaning to block focus time but never get around to it, or if your meeting load shifts week to week so a fixed recurring block doesn't fit. It rebuilds your defenses every week based on actual load.

How it works

  1. 1A weekly Sunday schedule triggers the run.
  2. 2The flow reads all events for the upcoming week from Google Calendar.
  3. 3A logic step computes per-day meeting density and picks the lightest morning windows that meet a minimum length.
  4. 4It creates focus-block events on those windows, marked busy and visibility-private, skipping days already saturated with meetings.
  5. 5A recap of the blocks created is posted to your Slack so you know where your protected time landed.

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.