PERSONAL PRODUCTIVITY

Schedule protected deep-work blocks every morning

Runs on a daily schedule before your workday starts, finds the longest open gap in your calendar.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionRead today's events and find the longest free gapGoogle CalendarGoogle Calendar
  • LogicBranch: is the gap long enough to protect?
  • ActionBook a private deep-work block in the gapGoogle CalendarGoogle Calendar
  • ActionSet Slack status and Do Not Disturb for the blockSlack
  • OutputConfirm the protected block in SlackSlack

What it does

Each morning this workflow scans the day ahead, locates your largest uninterrupted free window, and books a deep-work block into it before meetings have a chance to claim it. It then sets your Slack status and Do Not Disturb to match the block so colleagues see you're heads-down.

When to use it

Use it when you keep meaning to protect focus time but never get to it before the calendar fills. Proactively claiming the slot each morning beats fighting for it at noon.

How it works

  1. 1A scheduled trigger fires early each weekday morning.
  2. 2The workflow reads the day's Google Calendar events and computes the longest free gap within your working hours.
  3. 3A branch confirms the gap meets your minimum length (e.g. 90 minutes); if nothing qualifies, the run ends quietly.
  4. 4It creates a calendar event titled "Deep Work — do not book" set to busy/private for that window.
  5. 5It sets your Slack status to focusing and schedules Do Not Disturb to cover the exact block, then posts a confirmation to your personal channel.

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.