PERSONAL PRODUCTIVITY

Weekly low-attendance standing-meeting flagger

Every Monday, scans the next 7 days of recurring calendar events, finds standing meetings where accepted attendance keeps falling below a threshold.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule fires
  • ActionFetch next 7 days of eventsGoogle CalendarGoogle Calendar
  • LogicKeep recurring meetings only
  • LogicCompute accepted-attendee ratio
  • LogicFilter below acceptance threshold
  • OutputPost ranked cancel-candidate digest to SlackSlack

What it does

Runs a weekly audit of your recurring meetings and surfaces the ones that are quietly wasting time. It looks only at standing (recurring) events, measures how many invitees actually accepted versus the headcount, and flags every meeting that drops below a configurable acceptance threshold (default 50%). The result is a ranked Slack digest the ops or chief-of-staff team can act on in minutes.

When to use it

Use it when calendar bloat is real but nobody owns the cleanup. Good for operations leads, EAs, and chiefs of staff who want a standing nudge to kill or shrink meetings that lost their quorum, without manually opening every recurring series.

How it works

  1. 1A Monday morning schedule fires the audit.
  2. 2Pull the next 7 days of events from Google Calendar and keep only recurring ones.
  3. 3For each series, compute the accepted-attendee ratio against total invitees.
  4. 4Filter to meetings below the acceptance threshold.
  5. 5Post a ranked digest to Slack listing each flagged meeting, its organizer, and its acceptance rate for a cancel/keep decision.

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.