PERSONAL PRODUCTIVITY

Weekly meeting-load report to Notion with overload flags

Every Friday it tallies your week's meetings by hours, count, and recurring vs one-off, writes a structured report into a Notion database.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFriday afternoon schedule
  • ActionPull the week's events and aggregate meeting metricsGoogle CalendarGoogle Calendar
  • LogicFlag overloaded days and worst recurring series
  • ActionWrite the structured report into a Notion databaseNotionNotion
  • OutputShare the report link in SlackSlack

What it does

At the end of each week this workflow analyzes how your time actually went: total meeting hours, number of meetings, share of recurring vs ad-hoc, and the longest unbroken focus stretch you got. It writes a dated entry into a Notion database and highlights the worst-overloaded days.

When to use it

Use it when you suspect meetings are eating your week but lack the data to push back. A weekly trend record turns a vague feeling into evidence for trimming recurring invites.

How it works

  1. 1A scheduled trigger fires Friday afternoon.
  2. 2The workflow pulls the week's events from Google Calendar and aggregates hours, counts, and recurring/one-off split per day.
  3. 3A branch tags any day that exceeded your focus budget and identifies recurring series that are the biggest offenders.
  4. 4It creates a new page in a Notion database with the metrics, the overload flags, and a short list of suggested invites to renegotiate.
  5. 5It posts the report link to Slack so the summary lands where you'll see it.

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
    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.