PERSONAL PRODUCTIVITY

Weekly Meeting-Load Audit with Decline Recommendations

Every Friday, scans next week's Google Calendar, scores each person's meeting load against a healthy threshold.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFriday weekly schedule fires
  • ActionFetch next week's events from Google CalendarGoogle CalendarGoogle Calendar
  • LogicTally hours per day vs focus budget
  • LogicFlag overloaded days and rank decline candidates
  • OutputPost per-person overload digest to SlackSlack

What it does

Runs a weekly audit of the upcoming week's calendar, measures how many hours are booked versus a configurable focus-time budget, and surfaces the worst offenders with concrete trim suggestions before the week starts.

When to use it

Use it when your team consistently runs out of deep-work time and you want a proactive, data-backed nudge instead of waiting for people to burn out. Best for managers or chiefs of staff auditing their own or a small team's load.

How it works

  1. 1A Friday-afternoon schedule fires the workflow.
  2. 2It pulls next week's events from Google Calendar for each tracked attendee.
  3. 3It tallies meeting hours per day and compares them to the focus-time budget.
  4. 4A logic step flags any day over threshold and ranks recurring or low-priority meetings as decline candidates.
  5. 5It drafts plain-language recommendations (decline, shorten to 25 min, or make async).
  6. 6A Slack message delivers the per-person digest with the flagged meetings.

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.