PERSONAL PRODUCTIVITY

Monthly Meeting-Load Report to a Notion Dashboard

On the first of each month, aggregates the prior month's meetings into totals by category, recurring-series cost, and reclaimable hours.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • Trigger1st-of-month schedule fires
  • ActionFetch prior-month eventsGoogle CalendarGoogle Calendar
  • LogicGroup by category and recurring series
  • LogicCompute totals and reclaimable hours
  • OutputWrite report page to Notion databaseNotionNotion

What it does

This workflow builds a monthly retrospective of where your time actually went. It reads every event from the previous calendar month, groups them by category and recurring series, and calculates total meeting hours, the share consumed by standing meetings, and an estimate of hours that could have been focus time. It writes the results as a new page in a Notion database so you keep a trend you can review over time.

When to use it

Use it when you want hard numbers for a monthly time-management review, a manager one-on-one, or a personal audit of which recurring meetings are quietly eating your month.

How it works

  1. 1A first-of-month schedule starts the report.
  2. 2It fetches all events from the prior month in Google Calendar.
  3. 3It categorizes each event and identifies recurring series by title and cadence.
  4. 4It computes totals: meeting hours, recurring-meeting cost, and estimated reclaimable hours.
  5. 5It assembles a structured summary with the heaviest series called out.
  6. 6It creates a new page in the Notion meeting-load database with all metrics filled in.

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.