PERSONAL PRODUCTIVITY

Auto-Insert Protected Focus Blocks for Light-Meeting Days

Each evening it checks tomorrow's calendar, and if the day has enough open space below the overload line.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvening schedule for next day
  • ActionFetch tomorrow's eventsGoogle CalendarGoogle Calendar
  • LogicFind gaps, skip if day over threshold
  • ActionName block and choose best gapOpenAI
  • ActionCreate protected busy focus blockGoogle CalendarGoogle Calendar
  • OutputConfirm the block in SlackSlack

What it does

This workflow protects deep-work time before the day fills up. Every evening it inspects the next day's events, and when the day is light enough to safely hold time, it writes a focus block directly into the largest open gap and marks it busy so colleagues cannot book over it. Days already at or above the overload threshold are skipped so it never adds to a crowded schedule.

When to use it

Use it when you want focus time defended automatically without a daily approval step, for people comfortable letting the workflow write to their calendar.

How it works

  1. 1An evening schedule fires for the next day.
  2. 2Google Calendar returns tomorrow's events.
  3. 3A logic step measures booked hours and finds open gaps; if the day exceeds the overload threshold it exits without acting.
  4. 4For qualifying days, an OpenAI step names the focus block based on the day's themes and picks the best gap.
  5. 5The focus block is created in Google Calendar as a busy hold.
  6. 6A confirmation noting the block time is sent to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.