PERSONAL PRODUCTIVITY

Weekly Low-Attendance Standing Meeting Scanner

Every Monday, scans all recurring meetings on a Google Calendar, flags the ones where fewer than half the invitees actually accepted.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Mon 7am)
  • ActionFetch recurring events + RSVP statusGoogle CalendarGoogle Calendar
  • LogicKeep meetings under 50% accepted
  • LogicRank by wasted person-hours
  • OutputPost cancel/shrink shortlist to SlackSlack

What it does

It finds the standing meetings that quietly stopped earning their place. Once a week it reads every recurring event on a shared Google Calendar, measures real acceptance against the invite list, and surfaces the worst offenders so an operator can act on them in minutes instead of guessing.

When to use it

Run this when your team's calendar has accumulated recurring syncs nobody remembers approving and you want a regular, low-effort nudge to prune them. Ideal for chiefs of staff, EAs, and ops leads who own meeting hygiene.

How it works

  1. 1A weekly schedule fires Monday at 7am.
  2. 2The flow pulls all recurring events for the next 7 days from Google Calendar, including attendee response status.
  3. 3A filter keeps only meetings where accepted invitees are below 50% of those invited, or where 3+ people declined.
  4. 4It ranks survivors by wasted person-hours (duration times no-show count).
  5. 5The top offenders are posted to a Slack channel as a tidy shortlist with a one-line cancel/shrink recommendation each.

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.