PERSONAL PRODUCTIVITY

Weekly report on how well your focus blocks were protected

Every Friday this scans the past week's calendar, measures how much protected focus time was kept versus eroded by overlapping meetings.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Friday afternoon)
  • ActionPull last 7 days of calendar eventsGoogle CalendarGoogle Calendar
  • LogicCompute protected vs eroded focus minutes
  • ActionAppend weekly scorecard row to NotionNotionNotion
  • OutputReturn link to Notion scorecard entryNotionNotion

What it does

Gives you a weekly accountability scorecard for your deep-work time. It tallies how many focus-block minutes you planned, how many survived intact, and how many were eaten by meetings booked over them. It then writes a dated entry to a Notion database so you can see the trend across weeks and spot which meetings keep encroaching.

When to use it

When you've set up focus blocks and want hard data on whether they're actually holding. Use it for a Friday retro or a manager one-on-one about protecting maker time.

How it works

  1. 1A weekly schedule fires Friday afternoon.
  2. 2The flow pulls the last seven days of events from Google Calendar.
  3. 3It separates focus-block holds from meetings and computes overlap minutes for each block.
  4. 4A summarization step derives protected-versus-eroded totals and lists the top encroaching meetings.
  5. 5It appends a new row to a Notion database with the week's date, protection rate, and offender list.
  6. 6The output is a link to the new Notion scorecard entry.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect NotionPages, databases, comments.
  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.