PERSONAL PRODUCTIVITY

Weekly Focus-Block Audit with Slack Digest

Every Friday, scans the upcoming work week's calendar and flags any day that has zero uninterrupted focus blocks of 90 minutes or more.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFriday afternoon schedule fires
  • ActionFetch next week's eventsGoogle CalendarGoogle Calendar
  • LogicCompute longest free block per day
  • LogicFlag days with no 90-min focus block
  • OutputPost ranked focus digest to SlackSlack

What it does

Runs a forward-looking audit of next week's calendar. It measures the gaps between scheduled meetings each day, identifies which days have no continuous free stretch of at least 90 minutes, and delivers a Slack digest ranking the most fragmented days so people can reclaim focus time before the week starts.

When to use it

Use it if your team treats deep work as a first-class commodity and wants a standing Friday checkpoint to catch over-booked weeks early. Ideal for engineering, design, and IC-heavy teams where back-to-back meetings quietly erase maker time.

How it works

  1. 1A schedule trigger fires every Friday afternoon.
  2. 2The flow pulls all events for the next Monday-Friday from Google Calendar.
  3. 3For each day it computes the longest uninterrupted free window between events and working hours.
  4. 4A logic step keeps only days whose largest free block is under 90 minutes.
  5. 5It ranks the flagged days by total meeting hours and fragmentation count.
  6. 6A formatted digest is posted to a Slack channel, naming each starved day and its longest available gap.

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.